ath9k: BH shouldn't be enabled when hardirqs are disabled.
authorSenthil Balasubramanian <senthilkumar@atheros.com>
Tue, 9 Dec 2008 11:53:33 +0000 (16:53 +0530)
committerJohn W. Linville <linville@tuxdriver.com>
Fri, 12 Dec 2008 19:01:37 +0000 (14:01 -0500)
commita07d3619faeea3f540dd55f86685136f8928b4ad
treed836b56689793fe6991cbce837a3387d4ad7bb15
parentb143923689fdcc8e56688f2506a11ff16e4cd20b
ath9k: BH shouldn't be enabled when hardirqs are disabled.

ath_tx_complete_buf uses a BH version of spinlock and so releasing
the lock enables BH which is incorrect when called from sta_notify
callback as MAC80211 disables hardirqs before the driver callback
is called.

As ath_tx_complete_buf is shared between user and softirq context
using normal spinlock may not be appropriate. Though the proper
fix would be to cleanup the context properly in the driver code,
this would be an interim fix to avoid kernel warning.

Signed-off-by: Senthil Balasubramanian <senthilkumar@atheros.com>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
drivers/net/wireless/ath9k/xmit.c