summaryrefslogtreecommitdiffstats
path: root/drivers/net/smsc911x.c
diff options
context:
space:
mode:
authorLuis R. Rodriguez <lrodriguez@atheros.com>2010-10-21 01:07:03 +0200
committerJohn W. Linville <linville@tuxdriver.com>2010-10-27 21:41:14 +0200
commit1e450285281bdf766272c181ecd43d4f2f0711ce (patch)
treec7c8cd58d3f08af970e93f3489450886e4489bec /drivers/net/smsc911x.c
parentiwlwifi: quiet a noisy printk (diff)
downloadlinux-1e450285281bdf766272c181ecd43d4f2f0711ce.tar.xz
linux-1e450285281bdf766272c181ecd43d4f2f0711ce.zip
ath9k: add locking for stopping RX
ath9k locks for starting RX but not for stopping RX. We could potentially run into a situation where tried to stop RX but immediately started RX. This allows for races on the the RX engine deciding what buffer we last left off on and could potentially cause ath9k to DMA into already free'd memory or in the worst case at a later time to already given memory to other drivers. Fix this by locking stopping RX. This is part of a series that will help resolve the bug: https://bugzilla.kernel.org/show_bug.cgi?id=14624 For more details about this issue refer to: http://marc.info/?l=linux-wireless&m=128629803703756&w=2 Cc: stable@kernel.org Cc: Ben Greear <greearb@candelatech.com> Cc: Kyungwan Nam <kyungwan.nam@atheros.com> Signed-off-by: Luis R. Rodriguez <lrodriguez@atheros.com> Tested-by: Ben Greear <greearb@candelatech.com> Signed-off-by: John W. Linville <linville@tuxdriver.com>
Diffstat (limited to 'drivers/net/smsc911x.c')
0 files changed, 0 insertions, 0 deletions