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: <f7848160905010619n74372488n45a7b7abccfe5ea7@mail.gmail.com>
Date:	Fri, 1 May 2009 09:19:08 -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:

> I'm not sure what makes you think that it even _should_ be reverted.
>  Just to make that clear: it should _not_ be reverted. How did you check
>  that it isn't reverted in compat-wireless anyway? Must have been by code
>  inspection since 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.

Well I have the 04-29 compat-wireless tree and it does not work - just
like mainline I get timeouts. I have not been able to download later
versions - clicking on the URL does nothing for some reason. (Besides
I do not normally track compat-wireless.)

So since I wasn't able to use the mainline for 2-3 days and I could
not find any regression/bug where it was mentioned the bug was fixed
in compat-wireless I thought it might be better to revert it until a
fix appears. (BTW, I just did a pull on Linus tree and the fix hasn't
made it there).

So unless I am being too unreasonable here I think reverting *was*
(not *is* of course now) the right thing to do based if nothing else,
on the fact that ath9k and iwlagn were unusable for 2+ days and not
everyone can be expected to run compat-wireless daily builds.

Any way now that we know there is a fix - I will wait for it to appear
in mainline.

Parag
--
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/