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: <alpine.LFD.2.01.0911030719430.31845@localhost.localdomain>
Date:	Tue, 3 Nov 2009 07:26:26 -0800 (PST)
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Marcel Holtmann <marcel@...tmann.org>
cc:	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, 3 Nov 2009, Marcel Holtmann wrote:
> 
> and can we please stop jumping the gun here and going past the subsystem
> maintainers. I think this happens a little bit too much lately.

NO!

Quite frankly, I'm very unhappy indeed with the maintainers when it comes 
to this bug:

 - it was introduced after -rc5

 - it's been bisected by multiple people 

 - I've seen one of the encounters with a person who bisected it, and the 
   author of the buggy commit just wanted "more information" after having 
   been told that small commit causes lockups.

In other words - the LAST thing we should do is to pat the subsystem 
maintainers on the back and say "good job".

The fact is, when somebody reports a major bug that is fixed by a revert, 
then I shoudl probably revert _more_ eagerly rather than less!

And subsystem maintainers should jump on it, not wait several days.

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