linux-kernel - Re: [PATCH 00/14] kconfig: streamline distro configs for testers

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:	Fri, 21 Aug 2009 22:39:49 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Steven Rostedt <rostedt@...dmis.org>
Cc:	linux-kernel@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	Peter Zijlstra <peterz@...radead.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Theodore Tso <tytso@....edu>,
	Arjan van de Ven <arjan@...radead.org>,
	Greg KH <greg@...ah.com>,
	"Luis R. Rodriguez" <mcgrof@...il.com>, zippel@...ux-m68k.org,
	linux-kbuild@...r.kernel.org, Sam Ravnborg <sam@...nborg.org>,
	Jonathan Corbet <corbet@....net>,
	Alan Jenkins <sourcejedi.lkml@...glemail.com>,
	Andi Kleen <andi@...stfloor.org>
Subject: Re: [PATCH 00/14] kconfig: streamline distro configs for testers


* Steven Rostedt <rostedt@...dmis.org> wrote:

> 
> On Fri, 21 Aug 2009, Steven Rostedt wrote:
> 
> > 
> > On Fri, 21 Aug 2009, Ingo Molnar wrote:
> > > > OK, I'll add that to my todo list. Note, it the local config is 
> > > > only as good as the starting .config. That is, it never touches =y 
> > > > settings, because it only uses loaded modules as a base. Thus if 
> > > > something is set to =y it will always be set to =y.
> > > > 
> > > > What would you have in mind. Just randomly enabling modules? If we 
> > > > enable a "y" config then the next local*config will still keep 
> > > > that set.
> > > 
> > > Why - isnt local*config picking up environmental (currently running 
> > > kernel) properties? I.e. it would always set those things that are 
> > > needed - and randomize the rest. Have i misunderstood how it works?
> > 
> > Yes, this is a simple script. The only thing it does to find out what is 
> > configured is run "lsmod". Others have tried (in vain) to be able to look 
> > into things like lspci and lsusb to figure out what options to enable, 
> > just to end up with something so complex that it doesn't work.
> 
> Just to make this clearer. Since the script only uses lsmod to 
> figure out what options are configured, only touching "=m" options 
> is safe. There's no good way to know if a "=y" option can be 
> disabled, so I just leave them as is. Unfortunatly, once you run 
> localyesconfig, the script will stop modifying it, since there are 
> no more "=m" options, nor will you have modules listed in "lsmod".

ah - indeed, i forgot that it bases its decision off /proc/config, 
if available, right?

Fair enough - forget my suggestion. It's good as-is.

	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/