<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/drivers/net, branch v3.0.18</title>
<subtitle>Linux kernel source tree</subtitle>
<id>https://git.amat.us/linux/atom/drivers/net?h=v3.0.18</id>
<link rel='self' href='https://git.amat.us/linux/atom/drivers/net?h=v3.0.18'/>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/'/>
<updated>2012-01-26T01:25:06Z</updated>
<entry>
<title>iwlegacy: 3945: fix hw passive scan on radar channels</title>
<updated>2012-01-26T01:25:06Z</updated>
<author>
<name>Stanislaw Gruszka</name>
<email>sgruszka@redhat.com</email>
</author>
<published>2011-12-23T07:13:50Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=e4ae34bbc7386489a0c8253f246e7a5d316f249a'/>
<id>urn:sha1:e4ae34bbc7386489a0c8253f246e7a5d316f249a</id>
<content type='text'>
commit 68acc4afb040d98ddfd2cae0de09e2f4e1ee127f upstream.

Patch fix firmware error on "iw dev wlan0 scan passive" for
hardware scanning (with disable_hw_scan=0 module parameter).

 iwl3945 0000:03:00.0: Microcode SW error detected. Restarting 0x82000008.
 iwl3945 0000:03:00.0: Loaded firmware version: 15.32.2.9
 iwl3945 0000:03:00.0: Start IWL Error Log Dump:
 iwl3945 0000:03:00.0: Status: 0x0002A2E4, count: 1
 iwl3945 0000:03:00.0: Desc       Time       asrtPC blink2 ilink1  nmiPC   Line
 iwl3945 0000:03:00.0: SYSASSERT     (0x5) 0041263900 0x13756 0x0031C 0x00000 764
 iwl3945 0000:03:00.0: Error Reply type 0x000002FC cmd C_SCAN (0x80) seq 0x443E ser 0x00340000
 iwl3945 0000:03:00.0: Command C_SCAN failed: FW Error
 iwl3945 0000:03:00.0: Can't stop Rx DMA.

We have disable ability to change passive scanning to active on
particular channel when traffic is detected on that channel. Otherwise
firmware will report error, when we try to do passive scan on radar
channels.

Reported-and-debugged-by: Pedro Francisco &lt;pedrogfrancisco@gmail.com&gt;
Signed-off-by: Stanislaw Gruszka &lt;sgruszka@redhat.com&gt;
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>iwlagn: check for SMPS mode</title>
<updated>2012-01-26T01:25:05Z</updated>
<author>
<name>Wey-Yi Guy</name>
<email>wey-yi.w.guy@intel.com</email>
</author>
<published>2011-11-10T14:55:04Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=dd558f1e43567fd51a258f61081809e60735f9f4'/>
<id>urn:sha1:dd558f1e43567fd51a258f61081809e60735f9f4</id>
<content type='text'>
commit b2ccccdca46273c7b321ecf5041c362cd950da20 upstream.

Check and report WARN only when its invalid

Resolves:
https://bugzilla.kernel.org/show_bug.cgi?id=42621
https://bugzilla.redhat.com/show_bug.cgi?id=766071

Signed-off-by: Wey-Yi Guy &lt;wey-yi.w.guy@intel.com&gt;
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;


</content>
</entry>
<entry>
<title>net: Fix driver name for mdio-gpio.c</title>
<updated>2012-01-26T01:25:03Z</updated>
<author>
<name>Dirk Eibach</name>
<email>eibach@gdsys.de</email>
</author>
<published>2011-10-18T03:04:11Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=d7531928ae349a5d59a6820bc3a5e46c9907f5ad'/>
<id>urn:sha1:d7531928ae349a5d59a6820bc3a5e46c9907f5ad</id>
<content type='text'>
commit f42af6c486aa5ca6ee62800cb45c5b252020509d upstream.

Since commit
"7488876... dt/net: Eliminate users of of_platform_{,un}register_driver"
there are two platform drivers named "mdio-gpio" registered.
I renamed the of variant to "mdio-ofgpio".

Signed-off-by: Dirk Eibach &lt;eibach@gdsys.de&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>rt2800pci: fix spurious interrupts generation</title>
<updated>2012-01-26T01:25:02Z</updated>
<author>
<name>Stanislaw Gruszka</name>
<email>sgruszka@redhat.com</email>
</author>
<published>2012-01-13T11:59:32Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=ac631973a9ad6bba3d666f687288ebeb819c0df0'/>
<id>urn:sha1:ac631973a9ad6bba3d666f687288ebeb819c0df0</id>
<content type='text'>
commit dfd00c4c8f3dfa1fd7cec45f83d98b2a49743dcd upstream.

Same devices can generate interrupt without properly setting bit in
INT_SOURCE_CSR register (spurious interrupt), what will cause IRQ line
will be disabled by interrupts controller driver.

We discovered that clearing INT_MASK_CSR stops such behaviour. We
previously first read that register, and then clear all know interrupt
sources bits and do not touch reserved bits. After this patch, we write
to all register content (I believe writing to reserved bits on that
register will not cause any problems, I tested that on my rt2800pci
device).

This fix very bad performance problem, practically making device
unusable (since worked without interrupts), reported in:
https://bugzilla.redhat.com/show_bug.cgi?id=658451

We previously tried to workaround that issue in commit
4ba7d9997869d25bd223dea7536fc1ce9fab3b3b "rt2800pci: handle spurious
interrupts", but it was reverted in commit
82e5fc2a34fa9ffea38f00c4066b7e600a0ca5e6
as thing, that will prevent to detect real spurious interrupts.

Reported-and-tested-by: Amir Hedayaty &lt;hedayaty@gmail.com&gt;
Signed-off-by: Stanislaw Gruszka &lt;sgruszka@redhat.com&gt;
Acked-by: Gertjan van Wingerde &lt;gwingerde@gmail.com&gt;
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>rtl8192se: Fix BUG caused by failure to check skb allocation</title>
<updated>2012-01-26T01:24:42Z</updated>
<author>
<name>Larry Finger</name>
<email>Larry.Finger@lwfinger.net</email>
</author>
<published>2012-01-05T02:50:47Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=93d150e945fdaceb9e8fe18c7b9014569123195d'/>
<id>urn:sha1:93d150e945fdaceb9e8fe18c7b9014569123195d</id>
<content type='text'>
commit d90db4b12bc1b9b8a787ef28550fdb767ee25a49 upstream.

When downloading firmware into the device, the driver fails to check the
return when allocating an skb. When the allocation fails, a BUG can be
generated, as seen in https://bugzilla.redhat.com/show_bug.cgi?id=771656.

Signed-off-by: Larry Finger &lt;Larry.Finger@lwfinger.net&gt;
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>bonding: fix error handling if slave is busy (v2)</title>
<updated>2012-01-12T19:35:44Z</updated>
<author>
<name>stephen hemminger</name>
<email>shemminger@vyatta.com</email>
</author>
<published>2011-12-31T13:26:46Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=81aaa36dde03db855fb233382c7667f98ac12659'/>
<id>urn:sha1:81aaa36dde03db855fb233382c7667f98ac12659</id>
<content type='text'>
commit f7d9821a6a9c83450ac35e76d3709e32fd38b76f upstream.

If slave device already has a receive handler registered, then the
error unwind of bonding device enslave function is broken.

The following will leave a pointer to freed memory in the slave
device list, causing a later kernel panic.
# modprobe dummy
# ip li add dummy0-1 link dummy0 type macvlan
# modprobe bonding
# echo +dummy0 &gt;/sys/class/net/bond0/bonding/slaves

The fix is to detach the slave (which removes it from the list)
in the unwind path.

Signed-off-by: Stephen Hemminger &lt;shemminger@vyatta.com&gt;
Reviewed-by: Nicolas de Pesloüan &lt;nicolas.2p.debian@free.fr&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>asix: fix infinite loop in rx_fixup()</title>
<updated>2012-01-12T19:35:43Z</updated>
<author>
<name>Aurelien Jacobs</name>
<email>aurel@gnuage.org</email>
</author>
<published>2012-01-07T20:15:16Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=2643bcef53a08c09975861ebbed6d687571a2751'/>
<id>urn:sha1:2643bcef53a08c09975861ebbed6d687571a2751</id>
<content type='text'>
commit 6c15d74defd38e7e7f8805392578b7a1d508097e upstream.

At this point if skb-&gt;len happens to be 2, the subsequant skb_pull(skb, 4)
call won't work and the skb-&gt;len won't be decreased and won't ever reach 0,
resulting in an infinite loop.

With an ASIX 88772 under heavy load, without this patch, rx_fixup() reaches
an infinite loop in less than a minute. With this patch applied,
no infinite loop even after hours of heavy load.

Signed-off-by: Aurelien Jacobs &lt;aurel@gnuage.org&gt;
Cc: Jussi Kivilinna &lt;jussi.kivilinna@mbnet.fi&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;

</content>
</entry>
<entry>
<title>asix: new device id</title>
<updated>2012-01-12T19:35:04Z</updated>
<author>
<name>Aurelien Jacobs</name>
<email>aurel@gnuage.org</email>
</author>
<published>2011-12-16T10:49:22Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=e50262ea574d1daf62529e2b282b8551790f7f38'/>
<id>urn:sha1:e50262ea574d1daf62529e2b282b8551790f7f38</id>
<content type='text'>
commit e8303a3b2196272c3eb994d0fd1a189a958a2bdd upstream.

Adds the device id needed for the USB Ethernet Adapter delivered by
ASUS with their Zenbook.

Signed-off-by: Aurelien Jacobs &lt;aurel@gnuage.org&gt;
Acked-by: Grant Grundler &lt;grundler@chromium.org&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>wl12xx: Check buffer bound when processing nvs data</title>
<updated>2012-01-12T19:35:02Z</updated>
<author>
<name>Pontus Fuchs</name>
<email>pontus.fuchs@gmail.com</email>
</author>
<published>2011-10-18T07:23:42Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=a7b8c32b67b60fe9e8b53bb86bb7a04631e6e262'/>
<id>urn:sha1:a7b8c32b67b60fe9e8b53bb86bb7a04631e6e262</id>
<content type='text'>
commit f6efe96edd9c41c624c8f4ddbc4930c1a2d8f1e1 upstream.

An nvs with malformed contents could cause the processing of the
calibration data to read beyond the end of the buffer. Prevent this
from happening by adding bound checking.

Signed-off-by: Pontus Fuchs &lt;pontus.fuchs@gmail.com&gt;
Reviewed-by: Luciano Coelho &lt;coelho@ti.com&gt;
Signed-off-by: Luciano Coelho &lt;coelho@ti.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>wl12xx: Validate FEM index from ini file and FW</title>
<updated>2012-01-12T19:35:01Z</updated>
<author>
<name>Pontus Fuchs</name>
<email>pontus.fuchs@gmail.com</email>
</author>
<published>2011-10-18T07:23:41Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=4b2bb3c98c134fb26332afd5ad54078c53a30c44'/>
<id>urn:sha1:4b2bb3c98c134fb26332afd5ad54078c53a30c44</id>
<content type='text'>
commit 2131d3c2f99b081806fdae7662c92fe6acda52af upstream.

Check for out of bound FEM index to prevent reading beyond ini
memory end.

Signed-off-by: Pontus Fuchs &lt;pontus.fuchs@gmail.com&gt;
Reviewed-by: Luciano Coelho &lt;coelho@ti.com&gt;
Signed-off-by: Luciano Coelho &lt;coelho@ti.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
</feed>
