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] [thread-next>] [day] [month] [year] [list]
Message-ID: <1284474988.3704.10.camel@jlt3.sipsolutions.net>
Date:	Tue, 14 Sep 2010 16:36:28 +0200
From:	Johannes Berg <johannes@...solutions.net>
To:	"Michael S. Tsirkin" <mst@...hat.com>
Cc:	linux-kernel@...r.kernel.org,
	"John W. Linville" <linville@...driver.com>,
	"David S. Miller" <davem@...emloft.net>,
	linux-wireless@...r.kernel.org, netdev@...r.kernel.org,
	Reinette Chatre <reinette.chatre@...el.com>,
	Wey-Yi Guy <wey-yi.w.guy@...el.com>,
	Intel Linux Wireless <ilw@...ux.intel.com>,
	Stanislaw Gruszka <sgruszka@...hat.com>
Subject: Re: 2.6.36-rc4/iwl: warning triggered in net/mac80211/scan.c:266

On Tue, 2010-09-14 at 16:28 +0200, Michael S. Tsirkin wrote:
> I am running 2.6.36-rc4 on T60 with an iwlagn wireless card:
> 03:00.0 Network controller: Intel Corporation PRO/Wireless 5100 AGN [Shiloh] Network Connection
> 
> I was compiling a large file which stressed the box heavily, and the
> following warning in net/mac80211/scan.c triggered:
> 
>         /*
>          * It's ok to abort a not-yet-running scan (that
>          * we have one at all will be verified by checking
>          * local->scan_req next), but not to complete it
>          * successfully.
>          */
>         if (WARN_ON(!local->scanning && !aborted))
>                 aborted = true;
> 
> dmesg below:
> 
> [84379.361297] ------------[ cut here ]------------
> [84379.361307] WARNING: at net/mac80211/scan.c:266 ieee80211_scan_completed+0x43/0x17f()

> Should this happen? Does anyone care?
> I am not sure how reproducible this is.

No, it shouldn't happen. But there are various races in iwlwifi that can
cause this. Stanislaw has fixed them recently, but it's a fairly large
patchset. I'm not sure, but I don't think this is really new in .36.

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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ