linux-kernel - Re: [git pull] x86 changes for v2.6.27

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <487BBDCB.7050303@zytor.com>
Date:	Mon, 14 Jul 2008 13:57:47 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
CC:	Ingo Molnar <mingo@...e.hu>, linux-kernel@...r.kernel.org,
	Thomas Gleixner <tglx@...utronix.de>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [git pull] x86 changes for v2.6.27

Linus Torvalds wrote:
> 
> Things like this _really_ irritate me:
> 
> 	Memtest (MEMTEST) [Y/n/?] (NEW) ?
> 
> why the hell is that defaulting to "on"?
> 
> The rule of thumb should be:
> 
> 	NO NEW FEATURES SHOULD _EVER_ DEFAULT TO 'ON'!
> 
> I do realize that developers always think that _their_ particular cool new 
> feature is so important that it should default to 'on', but that's always 
> the case, and it's _always_ wrong.
> 

I'm a bit surprised that you'd say that for something that is a 
hardware-testing feature that needs a command-line option to be enabled 
at runtime.  I have always presumed that the default value is the 
recommended value, and I would think that that is what most people would 
assume.

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