linux-kernel - Re: [GIT PULL] tracing/urgent for v2.6.31

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] [day] [month] [year] [list]

Message-ID: <20090611102620.GB31719@elte.hu>
Date:	Thu, 11 Jun 2009 12:26:20 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	Steven Rostedt <rostedt@...dmis.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Frédéric Weisbecker <fweisbec@...il.com>
Subject: Re: [GIT PULL] tracing/urgent for v2.6.31

* Linus Torvalds <torvalds@...ux-foundation.org> wrote:

> On Wed, 10 Jun 2009, Steven Rostedt wrote:
> > 
> > Well it was:
> > 
> > 	default y if DEBUG_KERNEL
> > 
> > Where the rational was that if you want to debug the kernel, you 
> > might want to see some tracing features that are available to 
> > you.
> 
> Sure. I think that FTRACE config is borderline fine, although I 
> think tracing is pretty different from the debug options that 
> don't need the user to actually do anything (like 
> PAGEALLOC_DEBUG).
> 
> It's the other ones I think were clearly dubious (ok, the MARKERS 
> one isn't "clearly" dubious, since I have no idea why it got 
> enabled, so I guess it would count as "unclearly dubious" then).

I agree that we have too many default-y options - we'll have a sweep 
of all options and will default-disable the dubious (and unclearly 
dubious) ones in a way that truly re-triggers user selection even if 
the option is already enabled in the .config.

This particular new menu didnt actually change any of the existing 
options or defaults: it just organized/grouped an already existing, 
somewhat disorganized set of options and made it easier to disable 
them summarily. Making _that_ default-n could have caused people to 
accidentally disable a lot of options they had enabled in their 
configs intentionally.

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