linux-kernel - Re: kernel coding style for if ... else which cross #ifdef

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Sun, 25 May 2008 17:27:48 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Adrian Bunk <bunk@...nel.org>
CC:	Jeremy Fitzhardinge <jeremy@...p.org>,
	Tom Spink <tspink@...il.com>,
	Vegard Nossum <vegard.nossum@...il.com>,
	Sam Ravnborg <sam@...nborg.org>,
	Steve French <smfrench@...il.com>,
	lkml <linux-kernel@...r.kernel.org>
Subject: Re: kernel coding style for if ... else which cross #ifdef

Adrian Bunk wrote:
> 
> We do not have any serious problems where we actually depend on 
> randconfig.
> 
> randconfig is nice, but even if it would suddenly become no longer 
> available we wouldn't have significantely more build breakages in 
> stable kernels (perhaps a few more in the pathological cornercases
> only randconfig hits).
> 
> If this was really "the whole point" it wasn't not worth it.
> 
> Real value would come from getting errors for mistyped kconfig variable 
> names.
> 

Indeed.  However, getting at least compiler coverage across all branches 
of code is worth something, at least.

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