<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/drivers/net, branch v2.6.32</title>
<subtitle>Mirror of https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/
</subtitle>
<id>https://git.shady.money/linux/atom?h=v2.6.32</id>
<link rel='self' href='https://git.shady.money/linux/atom?h=v2.6.32'/>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/'/>
<updated>2009-12-01T00:47:16Z</updated>
<entry>
<title>Merge branch 'security' of git://git.kernel.org/pub/scm/linux/kernel/git/linville/wireless-2.6</title>
<updated>2009-12-01T00:47:16Z</updated>
<author>
<name>Linus Torvalds</name>
<email>torvalds@linux-foundation.org</email>
</author>
<published>2009-12-01T00:47:16Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=29e553631b2a0d4eebd23db630572e1027a9967a'/>
<id>urn:sha1:29e553631b2a0d4eebd23db630572e1027a9967a</id>
<content type='text'>
* 'security' of git://git.kernel.org/pub/scm/linux/kernel/git/linville/wireless-2.6:
  mac80211: fix spurious delBA handling
  mac80211: fix two remote exploits
</content>
</entry>
<entry>
<title>mac80211: fix spurious delBA handling</title>
<updated>2009-11-30T18:55:51Z</updated>
<author>
<name>Johannes Berg</name>
<email>johannes@sipsolutions.net</email>
</author>
<published>2009-11-22T11:28:41Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=827d42c9ac91ddd728e4f4a31fefb906ef2ceff7'/>
<id>urn:sha1:827d42c9ac91ddd728e4f4a31fefb906ef2ceff7</id>
<content type='text'>
Lennert Buytenhek noticed that delBA handling in mac80211
was broken and has remotely triggerable problems, some of
which are due to some code shuffling I did that ended up
changing the order in which things were done -- this was

  commit d75636ef9c1af224f1097941879d5a8db7cd04e5
  Author: Johannes Berg &lt;johannes@sipsolutions.net&gt;
  Date:   Tue Feb 10 21:25:53 2009 +0100

    mac80211: RX aggregation: clean up stop session

and other parts were already present in the original

  commit d92684e66091c0f0101819619b315b4bb8b5bcc5
  Author: Ron Rindjunsky &lt;ron.rindjunsky@intel.com&gt;
  Date:   Mon Jan 28 14:07:22 2008 +0200

      mac80211: A-MPDU Tx add delBA from recipient support

The first problem is that I moved a BUG_ON before various
checks -- thereby making it possible to hit. As the comment
indicates, the BUG_ON can be removed since the ampdu_action
callback must already exist when the state is != IDLE.

The second problem isn't easily exploitable but there's a
race condition due to unconditionally setting the state to
OPERATIONAL when a delBA frame is received, even when no
aggregation session was ever initiated. All the drivers
accept stopping the session even then, but that opens a
race window where crashes could happen before the driver
accepts it. Right now, a WARN_ON may happen with non-HT
drivers, while the race opens only for HT drivers.

For this case, there are two things necessary to fix it:
 1) don't process spurious delBA frames, and be more careful
    about the session state; don't drop the lock

 2) HT drivers need to be prepared to handle a session stop
    even before the session was really started -- this is
    true for all drivers (that support aggregation) but
    iwlwifi which can be fixed easily. The other HT drivers
    (ath9k and ar9170) are behaving properly already.

Reported-by: Lennert Buytenhek &lt;buytenh@marvell.com&gt;
Cc: stable@kernel.org
Signed-off-by: Johannes Berg &lt;johannes@sipsolutions.net&gt;
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
</content>
</entry>
<entry>
<title>b44: Fix wedge when using netconsole.</title>
<updated>2009-11-30T08:13:28Z</updated>
<author>
<name>David S. Miller</name>
<email>davem@davemloft.net</email>
</author>
<published>2009-11-30T08:13:28Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=0cae200eec6330cd2c20b24279597be1da50dc93'/>
<id>urn:sha1:0cae200eec6330cd2c20b24279597be1da50dc93</id>
<content type='text'>
Fixes kernel bugzilla #14691

Due to the way netpoll works, it is perfectly legal to see
NAPI already scheduled when new device events are pending
in b44_interrupt().

So logging a message about it is wrong and in fact harmful.

Based upon a patch by Andreas Mohr.

Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>wan: cosa: drop chan-&gt;wsem on error path</title>
<updated>2009-11-30T08:06:51Z</updated>
<author>
<name>Dan Carpenter</name>
<email>error27@gmail.com</email>
</author>
<published>2009-11-29T06:02:55Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=40be261dfd8bfba4baeff40168d44a6a4450ace1'/>
<id>urn:sha1:40be261dfd8bfba4baeff40168d44a6a4450ace1</id>
<content type='text'>
The other paths all drop chan-&gt;wsem.  This was found by a static
checker (smatch).

Signed-off-by: Dan Carpenter &lt;error27@gmail.com&gt;
Acked-by: Jan "Yenya" Kasprzak &lt;kas@fi.muni.cz&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>ep93xx-eth: check for zero MAC address on probe, not on device open</title>
<updated>2009-11-30T07:50:32Z</updated>
<author>
<name>Florian Fainelli</name>
<email>florian@openwrt.org</email>
</author>
<published>2009-11-28T13:57:00Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=3c91c7ae84966f992429e1e128c4936f22b89064'/>
<id>urn:sha1:3c91c7ae84966f992429e1e128c4936f22b89064</id>
<content type='text'>
If we happen to have registered the driver without passing
a MAC address, we will print a zero MAC address and register
the interface with this invalid address, this is confusin. This
patch moves the checking of a valid ethernet address and the
generation of a random one down from the open function to
the probe function.

Signed-off-by: Florian Fainelli &lt;florian@openwrt.org&gt;
Acked-by: Lennert Buytenhek &lt;buytenh@wantstofly.org&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>NET: smc91x: Fix irq flags</title>
<updated>2009-11-30T07:47:14Z</updated>
<author>
<name>Russell King - ARM Linux</name>
<email>linux@arm.linux.org.uk</email>
</author>
<published>2009-11-28T00:13:23Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=d5ccd67bb77ced5249067d05171992a7d5020393'/>
<id>urn:sha1:d5ccd67bb77ced5249067d05171992a7d5020393</id>
<content type='text'>
smc91x.h defines SMC_IRQ_FLAGS to be -1 when it wants the interrupt
flags to be taken from the resource structure.  However, d280ead
changed this to checking for non-zero resource flags.

Unfortunately, this means that on some platforms, we end up passing
'-1' to request_irq rather than the desired result.  Combine the two
conditions into one so that the IRQ flags are taken from the resource
if either SMC_IRQ_FLAGS is -1 or the resource flags specify an
interrupt trigger.

This restores network on at least the Versatile platform.

Signed-off-by: Russell King &lt;rmk+kernel@arm.linux.org.uk&gt;
Acked-by: Eric Miao &lt;eric.y.miao@gmail.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>smsc9420: prevent BUG() if ethtool is called with interface down</title>
<updated>2009-11-30T07:14:45Z</updated>
<author>
<name>Steve Glendinning</name>
<email>steve.glendinning@smsc.com</email>
</author>
<published>2009-11-30T07:14:45Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=6c53b1b15e222244358d3cbbefd2a13920faa352'/>
<id>urn:sha1:6c53b1b15e222244358d3cbbefd2a13920faa352</id>
<content type='text'>
This patch fixes a null pointer dereference BUG() if ethtool is used on
an smsc9420 interface while it is down, because the phy_dev is only
allocated while the interface is up.

Signed-off-by: Steve Glendinning &lt;steve.glendinning@smsc.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>r8169: restore mac addr in rtl8169_remove_one and rtl_shutdown</title>
<updated>2009-11-30T07:12:52Z</updated>
<author>
<name>Ivan Vecera</name>
<email>ivecera@redhat.com</email>
</author>
<published>2009-11-30T07:12:52Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=cc098dc705895f6b0109b7e8e026ac2b8ae1c0a1'/>
<id>urn:sha1:cc098dc705895f6b0109b7e8e026ac2b8ae1c0a1</id>
<content type='text'>
The newer chipsets (all PCI-E) are known that they need full power cycle
(AC or battery removal) to reset MAC address to a  hardwired one. Previous
patch to address this problem loads the original MAC address from EEPROM.
But it brought other problem for which it is necessary to introduce a new
module parameter.
However, it might suffice to restore the initial MAC address before
shutdown/reboot/kexec and when removing the module.

Signed-off-by: Ivan Vecera &lt;ivecera@redhat.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>e100: Use pci pool to work around GFP_ATOMIC order 5 memory allocation failure</title>
<updated>2009-11-30T01:17:29Z</updated>
<author>
<name>Roger Oksanen</name>
<email>roger.oksanen@cs.helsinki.fi</email>
</author>
<published>2009-11-30T01:17:29Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=98468efddb101f8a29af974101c17ba513b07be1'/>
<id>urn:sha1:98468efddb101f8a29af974101c17ba513b07be1</id>
<content type='text'>
pci_alloc_consistent uses GFP_ATOMIC allocation that may fail on some systems
with limited memory (Bug #14265). pci_pool_alloc allows waiting with
GFP_KERNEL.

Tested-by: Karol Lewandowski &lt;karol.k.lewandowski@gmail.com&gt;
Signed-off-by: Roger Oksanen &lt;roger.oksanen@cs.helsinki.fi&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>macvlan: fix gso_max_size setting</title>
<updated>2009-11-23T22:18:53Z</updated>
<author>
<name>Patrick McHardy</name>
<email>kaber@trash.net</email>
</author>
<published>2009-11-23T22:18:53Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=8c2acc53fd7987493f11640e266cf7130591e764'/>
<id>urn:sha1:8c2acc53fd7987493f11640e266cf7130591e764</id>
<content type='text'>
gso_max_size must be set based on the value of the underlying device to
support devices not using the full 64k.

Signed-off-by: Patrick McHardy &lt;kaber@trash.net&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
</feed>
