Re: Bug#562016: kernel WARNING in cfg80211 module

Johannes Berg
2009-12-22T09:10:34Z

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

Hi,

Thanks for the report.

On Mon, 2009-12-21 at 23:50 +0000, Ben Hutchings wrote:

> > [ 65.034652] ath0: direct probe to AP 00:11:95:77:e0:b0 (try 1)
> > [ 65.036737] ath0: direct probe responded
> > [ 65.036746] ath0: authenticate with AP 00:11:95:77:e0:b0 (try 1)
> > [ 65.038335] ath0: authenticated
> > [ 65.038367] ath0: associate with AP 00:11:95:77:e0:b0 (try 1)
> > [ 65.039861] ath0: deauthenticating from 00:11:95:77:e0:b0 by local choice (reason=3)
> > [ 65.039924] ath0: direct probe to AP 00:11:95:77:e0:b0 (try 1)
> > [ 65.040335] ath0: RX AssocResp from 00:11:95:77:e0:b0 (capab=0x421 status=0 aid=2)
> > [ 65.040342] ath0: associated
> > [ 65.041219] ------------[ cut here ]------------
> > [ 65.041255] WARNING: at
> /tmp/buildd/linux-2.6-2.6.32/debian/build/source_i386_none/net/wireles
> s/mlme.c:97 cfg80211_send_rx_assoc+0x14d/0x152 [cfg80211]()
> > [ 65.041263] Hardware name: 7658CTO

> > [ 65.041486] Pid: 761, comm: phy0 Not tainted 2.6.32-trunk-686 #1
> > [ 65.041491] Call Trace:
> > [ 65.041506] [<c1030a5d>] ? warn_slowpath_common+0x5e/0x8a
> > [ 65.041515] [<c1030a93>] ? warn_slowpath_null+0xa/0xc
> > [ 65.041540] [<f86cafc7>] ? cfg80211_send_rx_assoc+0x14d/0x152

> > [ 65.042191] ADDRCONF(NETDEV_CHANGE): ath0: link becomes ready
> > [ 65.057483] ath0: deauthenticating from 00:11:95:77:e0:b0 by
> local choice (reason=3)
> > [ 75.816298] ath0: no IPv6 routers present
> > [ 91.680596] e1000e 0000:00:19.0: irq 29 for MSI/MSI-X
> > [ 91.737568] e1000e 0000:00:19.0: irq 29 for MSI/MSI-X
> > [ 91.738236] ADDRCONF(NETDEV_UP): eth0: link is not ready
> > [ 91.906035] ADDRCONF(NETDEV_UP): ath0: link is not ready
> > [ 91.909344] ath0: direct probe to AP 00:11:95:77:e0:b0 (try 1)
> > [ 91.911254] ath0: direct probe responded
> > [ 91.911262] ath0: authenticate with AP 00:11:95:77:e0:b0 (try 1)
> > [ 91.912923] ath0: authenticated
> > [ 91.912958] ath0: associate with AP 00:11:95:77:e0:b0 (try 1)
> > [ 91.915043] ath0: RX ReassocResp from 00:11:95:77:e0:b0
> (capab=0x421 status=0 aid=2)
> > [ 91.915051] ath0: associated

This appears to be another race condition, note how the deauth request
comes between the assoc and assoc response. AFAICT it is mostly harmless
except confusing events will be sent to userspace. I'll look into fixing
it.

johannes

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