linux-kernel - Re: Additional kconfig targets (cloneconfig, nonint

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:	Sat, 3 May 2008 23:49:22 +0200
From:	Sam Ravnborg <sam@...nborg.org>
To:	Roman Zippel <zippel@...ux-m68k.org>
Cc:	linux-kbuild <linux-kbuild@...r.kernel.org>,
	LKML <linux-kernel@...r.kernel.org>,
	Dave Jones <davej@...emonkey.org.uk>,
	Roland McGrath <roland@...hat.com>,
	Andres Salomon <dilinger@...ued.net>
Subject: Re: Additional kconfig targets (cloneconfig, nonint_oldconfig etc)

Hi Roman.

> The patch I've seen for the last point put it into conf.c, which is the wrong 
> place for it. For this sort of thing we should create a small query tool, 
> which then can export all sorts of information.
> If we silence the defconfig output (which IMO is a good thing, as I don't 
> think anyone looked at the output seriously for a long time and the current 
> behaviour has purely historical reasons), it would also open up the 
> possibility to separate it from conf.c.

aconf is now ready to take care of defconfig, randconfig and all*config.
That leaves us with two simple tasks for conf.c:
config and oldconfig

[silentoldconfig is gone as oldconfig is 'silent' now].

aconf can take a base config for all the targets and avoids being
clever where to locate it. (Read: does not use DEFCONFIG_LIST).

I dunno if this is what you had in mind but I certainly like the result.
A cleaned up set of patches will soon hit the kbuild list.

> This also fits into an idea I'm playing with to extend the .config format like 
> this:
> 
> %defaultmode: mod
> CONFIG_FOO=n
> 
I understand the solution that you describe but I fail to see the
usefulness of it.
Can I request you to elaborate a bit more how you see it used.
I can give it a shot if I see it solving a real issue.

> Basically this could replace "make allmodconfig KCONFIG_ALLCONFIG=..." and the 
> current way to produce an allmodconfig would be replaced by a dedicated 
> function.
This part I did not understand either. I am aware of the current behaviour
but do not get the "dedicated function" thing.

Thanks in advance,

	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/