linux-kernel - Re: Please consider reverting 7d930bc33653d5592dc386a76a38f39c2e962344

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: <43e72e890911030955j63483919h9759fbb0b5e7acc3@mail.gmail.com>
Date:	Tue, 3 Nov 2009 09:55:28 -0800
From:	"Luis R. Rodriguez" <mcgrof@...il.com>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	Ingo Molnar <mingo@...e.hu>, Marcel Holtmann <marcel@...tmann.org>,
	Dmitry Torokhov <dmitry.torokhov@...il.com>,
	David Miller <davem@...emloft.net>, johannes@...solutions.net,
	linville@...driver.com, linux-kernel@...r.kernel.org,
	linux-wireless@...r.kernel.org
Subject: Re: Please consider reverting 7d930bc33653d5592dc386a76a38f39c2e962344

On Tue, Nov 3, 2009 at 9:37 AM, Linus Torvalds
<torvalds@...ux-foundation.org> wrote:
>
>
> On Tue, 3 Nov 2009, Luis R. Rodriguez wrote:
>>
>> How this sort of issue is dealt with is subjective and it is up to
>> maintainers to deal with.
>
> Not when they then complain when others hit the same issue several days
> later.
>
>> Having more information on the patch and better communication about
>> the issue it solved, and the issues that reverting it would have
>> caused would certainly have helped maintainers make a better call at a
>> regression caused by it but knowing Johannes he'd probably cook up a
>> followup fix ASAP and that is exactly what he did.
>
> He may have cooked it up, but he didn't send it to me, and he didn't even
> bother to post it as a response to people who complained about the same
> commit.
>
> The fact that people on the wireless mailing lists may have known about
> this just makes things _worse_, I think. It shows that we really _need_ to
> go around maintainers, when not going around them seems to result in days
> of delays and total waste of time for everybody.

Well I wouldn't quite say that. Me and Johannes know about it, I
cannot say everyone else who reads linux-wireless understood the
issue. I was trying to explain that the root cause of this whole issue
was non-obvious and even when I found a fix that worked for me it
turned out that wasn't the "proper" solution. So in reality the only
one who probably really understood this issue inside out and backwards
was Johannes.

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