linux-kernel - Re: [PATCH] Add rdc321x defconfig file

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, 25 Feb 2008 12:17:07 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Adrian Bunk <bunk@...nel.org>
Cc:	Florian Fainelli <florian.fainelli@...ecomint.eu>,
	linux-kernel@...r.kernel.org, Sam Ravnborg <sam@...nborg.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	"H. Peter Anvin" <hpa@...or.com>
Subject: Re: [PATCH] Add rdc321x defconfig file

* Adrian Bunk <bunk@...nel.org> wrote:

> What I want is that e.g. after fiddling with kernel headers I want an 
> easy way of having much compile coverage. And my script that builds 
> all defconfig's is trivial (although it takes a day to finish).

no, i think you misunderstood me. I do allyesconfig testing to make sure 
the kernel is still generic enough on PC hardware - not to catch build 
breakage.

What i do against build breakage is randconfig testing. That catches far 
more build breakage than a few limited number of defconfigs would ever.

More defconfigs would just be a constant maintenance drag, they are 
rather pointless on PC hardware anyway (we'd have to have at least a few 
hundred of them for it to be meaningful as a "default config") and it 
does not really solve the problem either.

	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/