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

Message-ID: <20080227183128.GA12411@uranus.ravnborg.org>
Date:	Wed, 27 Feb 2008 19:31:28 +0100
From:	Sam Ravnborg <sam@...nborg.org>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	Adrian Bunk <bunk@...nel.org>,
	Florian Fainelli <florian.fainelli@...ecomint.eu>,
	linux-kernel@...r.kernel.org, Thomas Gleixner <tglx@...utronix.de>,
	"H. Peter Anvin" <hpa@...or.com>
Subject: Re: [PATCH] Add rdc321x defconfig file

> 
> what would be really useful is an automatic Kconfig tree analysis, with 
> the printing out of too deep dependencies perhaps? Which might result in 
> the breaking down of too deep dependencies - to increase the coverage of 
> randconfig testing. Sometimes the number of "depends on" conditions are 
> mind-blowing.

If I get into kconfig hacking again I will try to look into fixing
kconfig so we can have all Kconfig files in one hirachy.
This would gives us useful information such as dependencies on
unknow symbols and the like.

Statistics as you describe could be relevant to find bad
Kconfig design but I see this much more as a check thing
for bad design than something to make it easier to reach
more configs with 100 randconfigs.

Anyway - this is just vapourware until someone starts
to hack on kconfig.

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