linux-kernel - Re: new: regression iwl3945/mac80211 endless after suspend associate/deassociate loop

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: <20080902130429.GB19172@google.com>
Date:	Tue, 2 Sep 2008 16:04:31 +0300
From:	"Michael S. Tsirkin" <m.s.tsirkin@...il.com>
To:	Johannes Berg <johannes@...solutions.net>
Cc:	Zhu Yi <yi.zhu@...el.com>, "Rafael J. Wysocki" <rjw@...k.pl>,
	LKML <linux-kernel@...r.kernel.org>, reinette.chatre@...el.com,
	linux-wireless@...r.kernel.org,
	Jan-Espen Pettersen <sigsegv@...iotube.org>,
	"John W. Linville" <linville@...driver.com>
Subject: Re: new: regression iwl3945/mac80211 endless after suspend
	associate/deassociate loop

On Tue, Sep 02, 2008 at 08:10:09AM +0200, Johannes Berg wrote:
> Zhu Yi wrote:
> > On Mon, 2008-09-01 at 19:07 +0300, Michael S. Tsirkin wrote:
> >> [16482.909453] eth1: associate with AP XX:XX:XX:XX:XX:XX
> >> [16482.918553] eth1: RX ReassocResp from XX:XX:XX:XX:XX:XX
> >> (capab=0x411 status=0 aid=1)
> >> [16482.918564] eth1: associated
> >> [16492.920224] eth1: disassociating by local choice (reason=3)
> >> [16492.920986] eth1: disassociating by local choice (reason=3)
> >
> > It is exactly 10 seconds the local STA sends the deauth_leaving frame
> > before associated everytime. I wonder if it is the timeout for some
> > wireless config tools. NM?
> 
> "by local choice" means wext requested this, not a kernel bug.
> 
> johannes

Sure, it's wpa_supplicant in ubuntu gutsy doing it.

$wpa_supplicant -version
 wpa_supplicant v0.5.8
 Copyright (c) 2003-2007, Jouni Malinen <j@...fi> and contributors

But it happens to work fine without 8ab65b03b7893da4a49009e7e356e36e27b0c407.

So yes, this could be some assumption that wpa_supplicant makes and that
fails now. I guess I will try the latest version from source and report.
--
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/