Re: 2.6.32-rc4-git1 -- INFO: possible circular locking dependency detected

[Johannes Berg <johannes@sipsolutions.net>]

[-- Attachment #1: Type: text/plain, Size: 936 bytes --]

On Mon, 2009-10-12 at 08:28 -0400, Miles Lane wrote:
> [  823.466853] [ INFO: possible circular locking dependency detected ]
> [  823.466866] 2.6.32-rc4-git1 #2
> [  823.466873] -------------------------------------------------------
> [  823.466884] swapper/0 is trying to acquire lock:
> [  823.466893]  (&sta->lock){+.-...}, at: [<f857bda4>] sta_addba_resp_timer_expired+0x1b/0x50 [mac80211]
> [  823.466940]
> [  823.466943] but task is already holding lock:
> [  823.466953] (&sta->ampdu_mlme.tid_tx[tid]->addba_resp_timer){+.-...}, at: [<c1032f22>] run_timer_softirq+0x125/0x1e5
> [  823.466984]
> [  823.466987] which lock already depends on the new lock.

Thanks for the report, I'll have to take a look at it, but this appears
to be due to the del_timer_sync() in ieee80211_process_addba_resp().

Guess it never really happens that the AP doesn't respond quickly enough
so the timer hardly fires.

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 801 bytes --]