linux-kernel - Re: [PATCH 183/196] driver core: fix build with SYSFS=n

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, 25 Jan 2008 23:57:23 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Greg KH <gregkh@...e.de>
Cc:	linux-kernel@...r.kernel.org,
	Randy Dunlap <randy.dunlap@...cle.com>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH 183/196] driver core: fix build with SYSFS=n


* Greg KH <gregkh@...e.de> wrote:

> > Changes like this (and it now leaked into Linus' tree as well) kill 
> > bisectability.
> 
> The odds that a "normal" person has sysfs turned off and modules 
> enabled, trying to bisect things, is pretty slim :)

that "slim" combination is what i use for about 25% of all my bisections 
- i build, boot and stress-test randconfig configs.

If i find a problem with a given .config, i do _not_ go around and 
change the .config to make a bisection point work. (and the automated 
bisection scripts definitely wont do it either.)

so what is a 'weird config' to you is a real testing barrier for others. 
And crap like that quickly mounts up. Having a buildable and bootable 
kernel at every bisection point is a _must_.

Please! :-)

	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/