linux-kernel - Re: Slow DOWN, please!!!

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]

Date:	Wed, 30 Apr 2008 18:25:50 -0700 (PDT)
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Adrian Bunk <bunk@...nel.org>
cc:	Andrew Morton <akpm@...ux-foundation.org>, rjw@...k.pl,
	davem@...emloft.net, linux-kernel@...r.kernel.org,
	jirislaby@...il.com
Subject: Re: Slow DOWN, please!!!

On Thu, 1 May 2008, Adrian Bunk wrote:
> 
> One big problem I see is Linus wanting to merge all drivers regardless 
> of the quality.

That's not what I said.

What I said was that I think we get *better* quality by merging early.

In other words, you're turning the whole argument on its head, and 
incorrectly so.

I claim that you are the one that is arguing for *worse* quality, by 
arguing for a process that is KNOWN to tend to generate bad code 
(out-of-tree drivers) as opposed to one that tends to fix things over time 
(and note the "tends" in both cases - there are counter-examples, but 
the trend is so clear that anybody who disputes it would seem to be either 
blind or lying).

So here's my challenge: give me *one* reason to believe that quality 
improves more out-of-tree than it does in-tree, and then you'll have a 
point. But you'd better be able to explain the ton of historical data we 
have that proves otherwise.

Until you do that, your blathering is just that - total blathering. The 
process I advocate is the one that has historical data on its side. Yours 
is just a failed theory.

			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/