From: Felix Fietkau <nbd@openwrt.org>
To: Ben Greear <greearb@candelatech.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: recursive locking on wireless-testing.
Date: Thu, 18 Nov 2010 01:37:55 +0100 [thread overview]
Message-ID: <4CE47563.2090803@openwrt.org> (raw)
In-Reply-To: <4CE446E3.3090604@candelatech.com>
On 2010-11-17 10:19 PM, Ben Greear wrote:
> I found this while testing wpa_supplicant that shares scan results.
> The kernel has no scan-sharing hacks in it..just a few patches
> I've been using for a while (and the deadlock prevention patch
> previously mentioned in other threads).
>
>
> Nov 17 13:16:25 ath9k kernel: ieee80211 wiphy0: Removed STA 00:14:d1:c6:d2:54
> Nov 17 13:16:25 ath9k kernel: ieee80211 wiphy0: Destroyed STA 00:14:d1:c6:d2:54
>
> =============================================
> [ INFO: possible recursive locking detected ]
> 2.6.37-rc1-wl+ #48
> ---------------------------------------------
This should fix it. ath_tx_complete is already called with the txq locked.
--- a/drivers/net/wireless/ath/ath9k/xmit.c
+++ b/drivers/net/wireless/ath/ath9k/xmit.c
@@ -1830,10 +1830,8 @@ static void ath_tx_complete(struct ath_s
else {
q = skb_get_queue_mapping(skb);
if (txq == sc->tx.txq_map[q]) {
- spin_lock_bh(&txq->axq_lock);
if (WARN_ON(--txq->pending_frames < 0))
txq->pending_frames = 0;
- spin_unlock_bh(&txq->axq_lock);
}
ieee80211_tx_status(hw, skb);
next prev parent reply other threads:[~2010-11-18 0:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-17 21:19 recursive locking on wireless-testing Ben Greear
2010-11-18 0:37 ` Felix Fietkau [this message]
2010-11-18 0:42 ` Ben Greear
2010-11-18 0:55 ` Ben Greear
2010-11-18 9:53 ` Felix Fietkau
2010-11-18 18:15 ` Ben Greear
2010-11-19 23:12 ` Ben Greear
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4CE47563.2090803@openwrt.org \
--to=nbd@openwrt.org \
--cc=greearb@candelatech.com \
--cc=linux-wireless@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.