linux-kernel - Re: 3.3.0-rc6-next-20120305 - iwlwifi BUG sleeping function called from invalid context (2 similar ones)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Wed, 07 Mar 2012 14:51:12 +0100
From:	Johannes Berg <johannes@...solutions.net>
To:	Valdis.Kletnieks@...edu
Cc:	Wey-Yi Guy <wey-yi.w.guy@...el.com>,
	linux-wireless@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: 3.3.0-rc6-next-20120305 - iwlwifi BUG sleeping function called
 from invalid context (2 similar ones)

On Wed, 2012-03-07 at 08:24 -0500, Valdis.Kletnieks@...edu wrote:
> Seen in my dmesg, 3.3.0-rc6-next20120305.  Dell Latitude E6500,
> Intel 5100 wireless card.  Seems to be pretty reproducible.
> 
> Have hit this one 368 times in 10 hours of uptime:
> 
> [  159.765059] wlan0: authenticate with d8:c7:c8:81:98:f0
> [  159.767884] wlan0: send auth to d8:c7:c8:81:98:f0 (try 1/3)
> [  159.769451] wlan0: authenticated
> [  159.769870] wlan0: waiting for beacon from d8:c7:c8:81:98:f0
> [  159.881293] wlan0: associate with d8:c7:c8:81:98:f0 (try 1/3)
> [  159.883470] wlan0: RX AssocResp from d8:c7:c8:81:98:f0 (capab=0x511 status=0 aid=4)
> [  159.883474] wlan0: associated
> [  159.890205] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
> [  164.620017] BUG: sleeping function called from invalid context at drivers/net/wireless/iwlwifi/iwl-trans.h:459

Yeah, thanks for the report -- it's an erroneous might_sleep() in a
function that can't and won't sleep. There's a patch on the way to
remove it.

johannes

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/