linux-toradex.git/drivers/net, branch v2.6.34.8

drivers/net/wireless/p54/eeprom.c: Return -ENOMEM on memory allocation failure

2011-01-06T23:08:23+00:00

commit 0d91f22b75347d9503b17a42b6c74d3f7750acd6 upstream.

In this code, 0 is returned on memory allocation failure, even though other
failures return -ENOMEM or other similar values.

A simplified version of the semantic match that finds this problem is as
follows: (http://coccinelle.lip6.fr/)

// 
@@
expression ret;
expression x,e1,e2,e3;
@@

ret = 0
... when != ret = e1
*x = \(kmalloc\|kcalloc\|kzalloc\)(...)
... when != ret = e2
if (x == NULL) { ... when != ret = e3
  return ret;
}
// 

Signed-off-by: Julia Lawall 
Acked-by: Christian Lamparter 
Signed-off-by: John W. Linville 
Signed-off-by: Paul Gortmaker

p54usb: add five more USBIDs

2011-01-06T23:08:23+00:00

commit 1a92795dac419128eb511dce30a6aad672064b88 upstream.

Source:
http://www.wikidevi.com/wiki/Intersil/p54/usb/windows

Signed-off-by: Christian Lamparter 
Signed-off-by: John W. Linville 
Signed-off-by: Paul Gortmaker

p54usb: fix off-by-one on !CONFIG_PM

2011-01-06T23:08:23+00:00

commit 11791a6f7534906b4a01ffb54ba0b02ca39398ef upstream.

The ISL3887 chip needs a USB reset, whenever the
usb-frontend module "p54usb" is reloaded.

This patch fixes an off-by-one bug, if the user
is running a kernel without the CONFIG_PM option
set and for some reason (e.g.: compat-wireless)
wants to switch between different p54usb modules.

Signed-off-by: Christian Lamparter 
Signed-off-by: John W. Linville 
Signed-off-by: Paul Gortmaker

b44: fix carrier detection on bind

2011-01-06T23:08:16+00:00

commit bcf64aa379fcadd074449cbf0c049da70071b06f upstream.

For carrier detection to work properly when binding the driver with a cable
unplugged, netif_carrier_off() should be called after register_netdev(),
not before.

Signed-off-by: Paul Fertser 
Signed-off-by: David S. Miller 
Signed-off-by: Paul Gortmaker

r8169: allocate with GFP_KERNEL flag when able to sleep

2011-01-06T23:08:15+00:00

commit aeb19f6052b5e5c8a24aa444fbff73b84341beac upstream.

We have fedora bug report where driver fail to initialize after
suspend/resume because of memory allocation errors:
https://bugzilla.redhat.com/show_bug.cgi?id=629158

To fix use GFP_KERNEL allocation where possible.

Tested-by: Neal Becker 
Signed-off-by: Stanislaw Gruszka 
Acked-by: Eric Dumazet 
Signed-off-by: David S. Miller 
Signed-off-by: Paul Gortmaker

skge: add quirk to limit DMA

2011-01-06T23:08:15+00:00

commit 392bd0cb000d4aac9e88e4f50823db85e7220688 upstream.

Skge devices installed on some Gigabyte motherboards are not able to
perform 64 dma correctly due to board PCI implementation, so limit
DMA to 32bit if such boards are detected.

Bug was reported here:
https://bugzilla.redhat.com/show_bug.cgi?id=447489

Signed-off-by: Stanislaw Gruszka 
Tested-by: Luya Tshimbalanga 
Signed-off-by: David S. Miller 
Signed-off-by: Paul Gortmaker

netxen: dont set skb->truesize

2011-01-06T23:08:14+00:00

commit 7e96dc7045bff8758804b047c0dfb6868f182500 upstream.

skb->truesize is set in core network.

Dont change it unless dealing with fragments.

Signed-off-by: Eric Dumazet 
Signed-off-by: David S. Miller 
Signed-off-by: Paul Gortmaker

atl1: fix resume

2011-01-06T23:08:12+00:00

commit ec5a32f67c603b11d68eb283d94eb89a4f6cfce1 upstream.

adapter->cmb.cmb is initialized when the device is opened and freed when
it's closed. Accessing it unconditionally during resume results either
in a crash (NULL pointer dereference, when the interface has not been
opened yet) or data corruption (when the interface has been used and
brought down adapter->cmb.cmb points to a deallocated memory area).

Signed-off-by: Luca Tettamanti 
Acked-by: Chris Snook 
Signed-off-by: David S. Miller 
Signed-off-by: Paul Gortmaker

hostap_pci: set dev->base_addr during probe

2011-01-06T23:08:04+00:00

commit 0f4da2d77e1bf424ac36424081afc22cbfc3ff2b upstream.

"hostap: Protect against initialization interrupt" (which reinstated
"wireless: hostap, fix oops due to early probing interrupt")
reintroduced Bug 16111.  This is because hostap_pci wasn't setting
dev->base_addr, which is now checked in prism2_interrupt.  As a result,
initialization was failing for PCI-based hostap devices.  This corrects
that oversight.

Signed-off-by: John W. Linville 
Signed-off-by: Paul Gortmaker

bonding: correctly process non-linear skbs

2011-01-06T23:07:58+00:00

commit ab12811c89e88f2e66746790b1fe4469ccb7bdd9 upstream.

It was recently brought to my attention that 802.3ad mode bonds would no
longer form when using some network hardware after a driver update.
After snooping around I realized that the particular hardware was using
page-based skbs and found that skb->data did not contain a valid LACPDU
as it was not stored there.  That explained the inability to form an
802.3ad-based bond.  For balance-alb mode bonds this was also an issue
as ARPs would not be properly processed.

This patch fixes the issue in my tests and should be applied to 2.6.36
and as far back as anyone cares to add it to stable.

Thanks to Alexander Duyck  and Jesse
Brandeburg  for the suggestions on this one.

Signed-off-by: Andy Gospodarek 
CC: Alexander Duyck 
CC: Jesse Brandeburg 
Signed-off-by: Jay Vosburgh 
Signed-off-by: David S. Miller 
Signed-off-by: Paul Gortmaker