linux-kernel - Re: Probe Timeouts with 47afbaf5af9454a7a1a64591e20cbfcc27ca67a8

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: <f7848160905011328o68010ba0rf8e18fa7ce88c7b5@mail.gmail.com>
Date:	Fri, 1 May 2009 16:28:01 -0400
From:	Parag Warudkar <parag.lkml@...il.com>
To:	Johannes Berg <johannes@...solutions.net>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	LKML <linux-kernel@...r.kernel.org>, niel.lambrechts@...il.com
Subject: Re: Probe Timeouts with 47afbaf5af9454a7a1a64591e20cbfcc27ca67a8

On 5/1/09, Johannes Berg <johannes@...solutions.net> wrote:
>How did you check that it isn't reverted in compat-wireless anyway?
>[..] if you had made an attempt to verify that the code in
> there works, you would have found that indeed there's no reason to
> revert this commit since the fix for it went in, and is literally a
> single line.

Johannes,

Just got around to downloading today's compat-wireless and it doesn't
work for me - frequent disconnects this time with response timeouts -

 9731.902114] wlan1: RX ReassocResp from 00:1e:e5:6a:2c:c2
(capab=0x411 status=0 aid=1)
[ 9731.902117] wlan1: associated
[ 9886.744022] wlan1: no probe response from AP 00:1e:e5:6a:2c:c2 -
disassociating
[ 9887.594299] wlan1: authenticate with AP 00:1e:e5:6a:2c:c2
[ 9887.596953] wlan1: authenticated
[ 9887.596958] wlan1: associate with AP 00:1e:e5:6a:2c:c2
[ 9887.600997] wlan1: RX ReassocResp from 00:1e:e5:6a:2c:c2
(capab=0x411 status=0 aid=1)
[ 9887.601000] wlan1: associated
[ 9930.640019] wlan1: no probe response from AP 00:1e:e5:6a:2c:c2 -
disassociating

Of course mainline continues to work fine after reverting
47afbaf5af9454a7a1a64591e20cbfcc27ca67a8.


No offense, but that to me is yet another reason to either revert or
get a proper fix in mainline whichever is sooner. (Sorry but
non-working network is impossible to live with - especially so when I
have to rely on mainline to get a working network (compat-wireless
doesn't work and the distro kernel just freezes when connecting to the
network and there is no fix in sight yet [*] ) )

Thanks
Parag

[*] https://bugs.launchpad.net/bugs/364333
--
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/