<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/drivers/net, branch v3.4.64</title>
<subtitle>Linux kernel source tree</subtitle>
<id>https://git.amat.us/linux/atom/drivers/net?h=v3.4.64</id>
<link rel='self' href='https://git.amat.us/linux/atom/drivers/net?h=v3.4.64'/>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/'/>
<updated>2013-10-01T16:10:52Z</updated>
<entry>
<title>sfc: Fix efx_rx_buf_offset() for recycled pages</title>
<updated>2013-10-01T16:10:52Z</updated>
<author>
<name>Ben Hutchings</name>
<email>bhutchings@solarflare.com</email>
</author>
<published>2013-09-06T21:39:20Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=43cbf1f46f0cdc56db7a424c6dda57bd9288376e'/>
<id>urn:sha1:43cbf1f46f0cdc56db7a424c6dda57bd9288376e</id>
<content type='text'>
This bug fix is only for stable branches older than 3.10.  The bug was
fixed upstream by commit 2768935a4660 ('sfc: reuse pages to avoid DMA
mapping/unmapping costs'), but that change is totally unsuitable for
stable.

Commit b590ace09d51 ('sfc: Fix efx_rx_buf_offset() in the presence of
swiotlb') added an explicit page_offset member to struct
efx_rx_buffer, which must be set consistently with the u.page and
dma_addr fields.  However, it failed to add the necessary assignment
in efx_resurrect_rx_buffer().  It also did not correct the calculation
of efx_rx_buffer::dma_addr in efx_resurrect_rx_buffer(), which assumes
that DMA-mapping a page will result in a page-aligned DMA address
(exactly what swiotlb violates).

Add the assignment of efx_rx_buffer::page_offset and change the
calculation of dma_addr to make use of it.

Signed-off-by: Ben Hutchings &lt;bhutchings@solarflare.com&gt;
Acked-by: David Miller &lt;davem@davemloft.net&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>rt2800: fix wrong TX power compensation</title>
<updated>2013-10-01T16:10:50Z</updated>
<author>
<name>Stanislaw Gruszka</name>
<email>sgruszka@redhat.com</email>
</author>
<published>2013-08-26T13:18:53Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=ebce1a846aa297022fc372d59e6829d0453125f2'/>
<id>urn:sha1:ebce1a846aa297022fc372d59e6829d0453125f2</id>
<content type='text'>
commit 6e956da2027c767859128b9bfef085cf2a8e233b upstream.

We should not do temperature compensation on devices without
EXTERNAL_TX_ALC bit set (called DynamicTxAgcControl on vendor driver).
Such devices can have totally bogus TSSI parameters on the EEPROM,
but still threaded by us as valid and result doing wrong TX power
calculations.

This fix inability to connect to AP on slightly longer distance on
some Ralink chips/devices.

Reported-and-tested-by: Fabien ADAM &lt;id2ndr@crocobox.org&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@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>net: usb: cdc_ether: Use wwan interface for Telit modules</title>
<updated>2013-10-01T16:10:50Z</updated>
<author>
<name>Fabio Porcedda</name>
<email>fabio.porcedda@gmail.com</email>
</author>
<published>2013-09-16T09:47:50Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=9f76c47a322910215c42c2e4226f2bef173c84ea'/>
<id>urn:sha1:9f76c47a322910215c42c2e4226f2bef173c84ea</id>
<content type='text'>
commit 0092820407901a0b2c4e343e85f96bb7abfcded1 upstream.

Signed-off-by: Fabio Porcedda &lt;fabio.porcedda@gmail.com&gt;
Acked-by: Oliver Neukum &lt;oliver@neukum.org&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>ath9k: avoid accessing MRC registers on single-chain devices</title>
<updated>2013-09-27T00:15:33Z</updated>
<author>
<name>Felix Fietkau</name>
<email>nbd@openwrt.org</email>
</author>
<published>2013-08-13T10:33:28Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=08c44ff3a4f24f11a05d9d7969f2d2cd7471beba'/>
<id>urn:sha1:08c44ff3a4f24f11a05d9d7969f2d2cd7471beba</id>
<content type='text'>
commit a1c781bb20ac1e03280e420abd47a99eb8bbdd3b upstream.

They are not implemented, and accessing them might trigger errors

Signed-off-by: Felix Fietkau &lt;nbd@openwrt.org&gt;
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>ath9k: fix rx descriptor related race condition</title>
<updated>2013-09-27T00:15:33Z</updated>
<author>
<name>Felix Fietkau</name>
<email>nbd@openwrt.org</email>
</author>
<published>2013-08-10T13:59:15Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=0f528a11451069fc6ea66c40fb9ab518e9d335b3'/>
<id>urn:sha1:0f528a11451069fc6ea66c40fb9ab518e9d335b3</id>
<content type='text'>
commit e96542e55a2aacf4bdeccfe2f17b77c4895b4df2 upstream.

Similar to a race condition that exists in the tx path, the hardware
might re-read the 'next' pointer of a descriptor of the last completed
frame. This only affects non-EDMA (pre-AR93xx) devices.

To deal with this race, defer clearing and re-linking a completed rx
descriptor until the next one has been processed.

Signed-off-by: Felix Fietkau &lt;nbd@openwrt.org&gt;
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>ath9k: always clear ps filter bit on new assoc</title>
<updated>2013-09-27T00:15:33Z</updated>
<author>
<name>Felix Fietkau</name>
<email>nbd@openwrt.org</email>
</author>
<published>2013-08-06T12:18:10Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=ad9e765fb1973bf8458f4d5ad88b59040992e0e3'/>
<id>urn:sha1:ad9e765fb1973bf8458f4d5ad88b59040992e0e3</id>
<content type='text'>
commit 026d5b07c03458f9c0ccd19c3850564a5409c325 upstream.

Otherwise in some cases, EAPOL frames might be filtered during the
initial handshake, causing delays and assoc failures.

Signed-off-by: Felix Fietkau &lt;nbd@openwrt.org&gt;
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>brcmsmac: Fix WARNING caused by lack of calls to dma_mapping_error()</title>
<updated>2013-09-27T00:15:33Z</updated>
<author>
<name>John W. Linville</name>
<email>linville@tuxdriver.com</email>
</author>
<published>2013-08-09T17:36:21Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=1df8b64670c1a8e848ff514d3640fffeb14e2435'/>
<id>urn:sha1:1df8b64670c1a8e848ff514d3640fffeb14e2435</id>
<content type='text'>
commit 67d0cf50bd32b66eab709871714e55725ee30ce4 upstream.

The driver fails to check the results of DMA mapping in twp places,
which results in the following warning:

[   28.078515] ------------[ cut here ]------------
[   28.078529] WARNING: at lib/dma-debug.c:937 check_unmap+0x47e/0x930()
[   28.078533] bcma-pci-bridge 0000:0e:00.0: DMA-API: device driver failed to check map error[device address=0x00000000b5d60d6c] [size=1876 bytes] [mapped as
 single]
[   28.078536] Modules linked in: bnep bluetooth vboxpci(O) vboxnetadp(O) vboxnetflt(O) vboxdrv(O) ipv6 b43 brcmsmac rtl8192cu rtl8192c_common rtlwifi mac802
11 brcmutil cfg80211 snd_hda_codec_conexant rng_core snd_hda_intel kvm_amd snd_hda_codec ssb kvm mmc_core snd_pcm snd_seq snd_timer snd_seq_device snd k8temp
 cordic joydev serio_raw hwmon sr_mod sg pcmcia pcmcia_core soundcore cdrom i2c_nforce2 i2c_core forcedeth bcma snd_page_alloc autofs4 ext4 jbd2 mbcache crc1
6 scsi_dh_alua scsi_dh_hp_sw scsi_dh_rdac scsi_dh_emc scsi_dh ata_generic pata_amd
[   28.078602] CPU: 1 PID: 2570 Comm: NetworkManager Tainted: G           O 3.10.0-rc7-wl+ #42
[   28.078605] Hardware name: Hewlett-Packard HP Pavilion dv2700 Notebook PC/30D6, BIOS F.27 11/27/2008
[   28.078607]  0000000000000009 ffff8800bbb03ad8 ffffffff8144f898 ffff8800bbb03b18
[   28.078612]  ffffffff8103e1eb 0000000000000002 ffff8800b719f480 ffff8800b7b9c010
[   28.078617]  ffffffff824204c0 ffffffff81754d57 0000000000000754 ffff8800bbb03b78
[   28.078622] Call Trace:
[   28.078624]  &lt;IRQ&gt;  [&lt;ffffffff8144f898&gt;] dump_stack+0x19/0x1b
[   28.078634]  [&lt;ffffffff8103e1eb&gt;] warn_slowpath_common+0x6b/0xa0
[   28.078638]  [&lt;ffffffff8103e2c1&gt;] warn_slowpath_fmt+0x41/0x50
[   28.078650]  [&lt;ffffffff8122d7ae&gt;] check_unmap+0x47e/0x930
[   28.078655]  [&lt;ffffffff8122de4c&gt;] debug_dma_unmap_page+0x5c/0x70
[   28.078679]  [&lt;ffffffffa04a808c&gt;] dma64_getnextrxp+0x10c/0x190 [brcmsmac]
[   28.078691]  [&lt;ffffffffa04a9042&gt;] dma_rx+0x62/0x240 [brcmsmac]
[   28.078707]  [&lt;ffffffffa0479101&gt;] brcms_c_dpc+0x211/0x9d0 [brcmsmac]
[   28.078717]  [&lt;ffffffffa046d927&gt;] ? brcms_dpc+0x27/0xf0 [brcmsmac]
[   28.078731]  [&lt;ffffffffa046d947&gt;] brcms_dpc+0x47/0xf0 [brcmsmac]
[   28.078736]  [&lt;ffffffff81047dcc&gt;] tasklet_action+0x6c/0xf0
--snip--
[   28.078974]  [&lt;ffffffff813891bd&gt;] SyS_sendmsg+0xd/0x20
[   28.078979]  [&lt;ffffffff81455c24&gt;] tracesys+0xdd/0xe2
[   28.078982] ---[ end trace 6164d1a08148e9c8 ]---
[   28.078984] Mapped at:
[   28.078985]  [&lt;ffffffff8122c8fd&gt;] debug_dma_map_page+0x9d/0x150
[   28.078989]  [&lt;ffffffffa04a9322&gt;] dma_rxfill+0x102/0x3d0 [brcmsmac]
[   28.079001]  [&lt;ffffffffa047a13d&gt;] brcms_c_init+0x87d/0x1100 [brcmsmac]
[   28.079010]  [&lt;ffffffffa046d851&gt;] brcms_init+0x21/0x30 [brcmsmac]
[   28.079018]  [&lt;ffffffffa04786e0&gt;] brcms_c_up+0x150/0x430 [brcmsmac]

As the patch adds a new failure mechanism to dma_rxfill(). When I changed the
comment at the start of the routine to add that information, I also polished
the wording.

Signed-off-by: Larry Finger &lt;Larry.Finger@lwfinger.net&gt;
Cc: Brett Rudley &lt;brudley@broadcom.com&gt;
Cc: Franky (Zhenhui) Lin &lt;frankyl@broadcom.com&gt;
Cc: Hante Meuleman &lt;meuleman@broadcom.com&gt;
Cc: brcm80211-dev-list@broadcom.com
Acked-by: Arend van Spriel &lt;arend@broadcom.com&gt;
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>macvtap: do not zerocopy if iov needs more pages than MAX_SKB_FRAGS</title>
<updated>2013-09-14T13:02:11Z</updated>
<author>
<name>Jason Wang</name>
<email>jasowang@redhat.com</email>
</author>
<published>2013-08-06T09:29:19Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=d60aa7fc969ffe14cac79b685aad011e66beb210'/>
<id>urn:sha1:d60aa7fc969ffe14cac79b685aad011e66beb210</id>
<content type='text'>
commit ece793fcfc417b3925844be88a6a6dc82ae8f7c6 upstream.

We try to linearize part of the skb when the number of iov is greater than
MAX_SKB_FRAGS. This is not enough since each single vector may occupy more than
one pages, so zerocopy_sg_fromiovec() may still fail and may break the guest
network.

Solve this problem by calculate the pages needed for iov before trying to do
zerocopy and switch to use copy instead of zerocopy if it needs more than
MAX_SKB_FRAGS.

This is done through introducing a new helper to count the pages for iov, and
call uarg-&gt;callback() manually when switching from zerocopy to copy to notify
vhost.

We can do further optimization on top.

This bug were introduced from b92946e2919134ebe2a4083e4302236295ea2a73
(macvtap: zerocopy: validate vectors before building skb).

Cc: Michael S. Tsirkin &lt;mst@redhat.com&gt;
Signed-off-by: Jason Wang &lt;jasowang@redhat.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>tun: signedness bug in tun_get_user()</title>
<updated>2013-09-14T13:02:09Z</updated>
<author>
<name>Dan Carpenter</name>
<email>dan.carpenter@oracle.com</email>
</author>
<published>2013-08-15T12:52:57Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=62d5a1d2a8a7c247c1f2dcd87b1e8c533b03017b'/>
<id>urn:sha1:62d5a1d2a8a7c247c1f2dcd87b1e8c533b03017b</id>
<content type='text'>
[ Upstream commit 15718ea0d844e4816dbd95d57a8a0e3e264ba90e ]

The recent fix d9bf5f1309 "tun: compare with 0 instead of total_len" is
not totally correct.  Because "len" and "sizeof()" are size_t type, that
means they are never less than zero.

Signed-off-by: Dan Carpenter &lt;dan.carpenter@oracle.com&gt;
Acked-by: Michael S. Tsirkin &lt;mst@redhat.com&gt;
Acked-by: Neil Horman &lt;nhorman@tuxdriver.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>8139cp: Fix skb leak in rx_status_loop failure path.</title>
<updated>2013-09-14T13:02:09Z</updated>
<author>
<name>Dave Jones</name>
<email>davej@redhat.com</email>
</author>
<published>2013-08-09T18:16:34Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=abdf975d2095b3f41939ec0e2259af5d485f2889'/>
<id>urn:sha1:abdf975d2095b3f41939ec0e2259af5d485f2889</id>
<content type='text'>
[ Upstream commit d06f5187469eee1b2932c02fd093d113cfc60d5e ]

Introduced in cf3c4c03060b688cbc389ebc5065ebcce5653e96
("8139cp: Add dma_mapping_error checking")

Signed-off-by: Dave Jones &lt;davej@redhat.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
</content>
</entry>
</feed>
