linux-kernel - Re: [PATCH] default to n for GROUP_SCHED and FAIR_GROUP

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:	Mon, 5 May 2008 13:48:31 -0700 (PDT)
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Ingo Molnar <mingo@...e.hu>
cc:	Arjan van de Ven <arjan@...radead.org>,
	Sam Ravnborg <sam@...nborg.org>,
	Parag Warudkar <parag.warudkar@...il.com>,
	LKML <linux-kernel@...r.kernel.org>,
	"akpm@...l.org" <akpm@...ux-foundation.org>,
	Peter Zijlstra <peterz@...radead.org>,
	Dave Jones <davej@...hat.com>
Subject: Re: [PATCH] default to n for GROUP_SCHED and FAIR_GROUP_SCHED

On Mon, 5 May 2008, Ingo Molnar wrote:
> 
> yeah, that's what i meant mostly - to new drivers we unfortunately 
> default to 'n'. And most of the time (i hope!) our defaults for new core 
> kernel and architectural features otherwise make sense.

I doubt it.

People are *way* too eager to mark things 'y', because it may make sense 
as a default to the developer of the feature, never mind that the average 
user should never *ever* enable it.

There are even things that are clearly marked experimental (and depend on 
the EXPERIMENTAL config option), and then have the gall to say "default 
y".

Another example of that kind of behaviour, for example, is just you 
fighting turning off 'default y' from FAIR_GROUP_SCHED, considering that 
it is known to cause latency problems and the reason isn't understood.

Developers want their features to be enabled. Regardless of whether they 
are features that make sense to normal people.

I'd love to make "default y" be something you must never do (except for 
question that don't get asked at all!), but that would just cause people 
to create negative config options ("disable my cool feature?") which we 
already have to some degree, and which is *really* irritating.

			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/