<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel.git/net/core/wireless.c, branch linux-2.6.21.y</title>
<subtitle>Hosts the 0x221E linux distro kernel.
</subtitle>
<id>https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-2.6.21.y</id>
<link rel='self' href='https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-2.6.21.y'/>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/'/>
<updated>2007-03-27T18:10:26Z</updated>
<entry>
<title>[PATCH] WE-22 : prevent information leak on 64 bit</title>
<updated>2007-03-27T18:10:26Z</updated>
<author>
<name>Jean Tourrilhes</name>
</author>
<published>2007-03-23T00:31:16Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=c2805fbb8630abb95d94ce7adc3f97976f7e0367'/>
<id>urn:sha1:c2805fbb8630abb95d94ce7adc3f97976f7e0367</id>
<content type='text'>
 	Johannes Berg discovered that kernel space was leaking to
userspace on 64 bit platform. He made a first patch to fix that. This
is an improved version of his patch.

Signed-off-by: Jean Tourrilhes &lt;jt@hpl.hp.com&gt;
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
</content>
</entry>
<entry>
<title>[PATCH] mark struct file_operations const 7</title>
<updated>2007-02-12T17:48:46Z</updated>
<author>
<name>Arjan van de Ven</name>
</author>
<published>2007-02-12T08:55:35Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=9a32144e9d7b4e21341174b1a83b82a82353be86'/>
<id>urn:sha1:9a32144e9d7b4e21341174b1a83b82a82353be86</id>
<content type='text'>
Many struct file_operations in the kernel can be "const".  Marking them const
moves these to the .rodata section, which avoids false sharing with potential
dirty data.  In addition it'll catch accidental writes at compile time to
these shared resources.

Signed-off-by: Arjan van de Ven &lt;arjan@linux.intel.com&gt;
Signed-off-by: Andrew Morton &lt;akpm@linux-foundation.org&gt;
Signed-off-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;
</content>
</entry>
<entry>
<title>[NET] CORE: Fix whitespace errors.</title>
<updated>2007-02-11T07:19:25Z</updated>
<author>
<name>YOSHIFUJI Hideaki</name>
</author>
<published>2007-02-09T14:24:36Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=4ec93edb14fe5fdee9fae6335f2cbba204627eac'/>
<id>urn:sha1:4ec93edb14fe5fdee9fae6335f2cbba204627eac</id>
<content type='text'>
Signed-off-by: YOSHIFUJI Hideaki &lt;yoshfuji@linux-ipv6.org&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>[NET]: Memory barrier cleanups</title>
<updated>2006-12-07T08:11:33Z</updated>
<author>
<name>Ralf Baechle</name>
</author>
<published>2006-12-07T08:11:33Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=e16aa207ccb61c5111525c462eeeba1f3f5fd370'/>
<id>urn:sha1:e16aa207ccb61c5111525c462eeeba1f3f5fd370</id>
<content type='text'>
I believe all the below memory barriers only matter on SMP so
therefore the smp_* variant of the barrier should be used.

I'm wondering if the barrier in net/ipv4/inet_timewait_sock.c should be
dropped entirely.  schedule_work's implementation currently implies a
memory barrier and I think sane semantics of schedule_work() should imply
a memory barrier, as needed so the caller shouldn't have to worry.
It's not quite obvious why the barrier in net/packet/af_packet.c is
needed; maybe it should be implied through flush_dcache_page?

Signed-off-by: Ralf Baechle &lt;ralf@linux-mips.org&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>[PATCH] wireless: WE-20 compatibility for ESSID and NICKN ioctls</title>
<updated>2006-10-19T21:08:19Z</updated>
<author>
<name>John W. Linville</name>
</author>
<published>2006-10-17T14:54:36Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=98978edb6278f0fb30c8d636c6a79a28f9164cb9'/>
<id>urn:sha1:98978edb6278f0fb30c8d636c6a79a28f9164cb9</id>
<content type='text'>
WE-21 changed the ABI for the SIOC[SG]IW{ESSID,NICKN} ioctls by dropping
NULL termination.  This patch adds compatibility code so that WE-21 can
work properly with WE-20 (and older) tools.

Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
</content>
</entry>
<entry>
<title>[PATCH] WE-21 support (core API)</title>
<updated>2006-09-25T20:52:14Z</updated>
<author>
<name>John W. Linville</name>
</author>
<published>2006-09-08T20:04:05Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=baef186519c69b11cf7e48c26e75feb1e6173baa'/>
<id>urn:sha1:baef186519c69b11cf7e48c26e75feb1e6173baa</id>
<content type='text'>
This is version 21 of the Wireless Extensions. Changelog :
	o finishes migrating the ESSID API (remove the +1)
	o netdev-&gt;get_wireless_stats is no more
	o long/short retry

This is a redacted version of a patch originally submitted by Jean
Tourrilhes.  I removed most of the additions, in order to minimize
future support requirements for nl80211 (or other WE successor).

CC: Jean Tourrilhes &lt;jt@hpl.hp.com&gt;
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
</content>
</entry>
<entry>
<title>[WIRELESS]: Convert notifications to use rtnl_notify()</title>
<updated>2006-09-22T21:55:00Z</updated>
<author>
<name>Thomas Graf</name>
</author>
<published>2006-08-15T07:36:49Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=bd5785ba3ac1c89aa4c351ceb2acd96686424d8c'/>
<id>urn:sha1:bd5785ba3ac1c89aa4c351ceb2acd96686424d8c</id>
<content type='text'>
Signed-off-by: Thomas Graf &lt;tgraf@suug.ch&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>[NET]: Remove unnecessary config.h includes from net/</title>
<updated>2006-09-22T21:54:21Z</updated>
<author>
<name>Dave Jones</name>
</author>
<published>2006-09-22T21:00:29Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=bf0d52492d82ad70684e17c8a46942c13d0e140e'/>
<id>urn:sha1:bf0d52492d82ad70684e17c8a46942c13d0e140e</id>
<content type='text'>
config.h is automatically included by kbuild these days.

Signed-off-by: Dave Jones &lt;davej@redhat.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>[PATCH] Send wireless netlink events with a clean slate</title>
<updated>2006-08-04T18:57:19Z</updated>
<author>
<name>Herbert Xu</name>
</author>
<published>2006-08-03T13:54:41Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=782a6675119c76c071e74e2ddd98268f47770cba'/>
<id>urn:sha1:782a6675119c76c071e74e2ddd98268f47770cba</id>
<content type='text'>
Drivers expect to be able to call wireless_send_event in arbitrary
contexts.  On the other hand, netlink really doesn't like being
invoked in an IRQ context.  So we need to postpone the sending of
netlink skb's to a tasklet.

Signed-off-by: Herbert Xu &lt;herbert@gondor.apana.org.au&gt;
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
</content>
</entry>
<entry>
<title>[PATCH] wext: Fix RtNetlink ENCODE security permissions</title>
<updated>2006-04-19T21:25:41Z</updated>
<author>
<name>Jean Tourrilhes</name>
</author>
<published>2006-04-14T17:47:26Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=848ef8555296f25d9226d3bc43ce4028835ed633'/>
<id>urn:sha1:848ef8555296f25d9226d3bc43ce4028835ed633</id>
<content type='text'>
	I've just realised that the RtNetlink code does not check the
permission for SIOCGIWENCODE and SIOCGIWENCODEEXT, which means that
any user can read the encryption keys. The fix is trivial and should
go in 2.6.17 alonside the two other patch I sent you last week.

Signed-off-by: Jean Tourrilhes &lt;jt@hpl.hp.com&gt;
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
</content>
</entry>
</feed>
