linux-kernel - Re: [PATCH] Fix corruption of CONFIG_X86

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, 30 May 2011 21:12:17 +0100 (BST)
From:	David Woodhouse <dwmw2@...radead.org>
To:	Ted Ts'o <tytso@....edu>
cc:	Ingo Molnar <mingo@...e.hu>, x86@...nel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Fix corruption of CONFIG_X86_32 in 'make oldconfig'

On Mon, 30 May 2011, Ted Ts'o wrote:

> So I could imagine two ways of doing this.  One would be a new file,
> .config-fixed, that contains a series of "CONFIG_XXX=[ymn]" which
> would have to be satisfied and which override what
> allyesconfig/allnoconfig/randconfig would otherwise do.

Which is apparently what KCONFIG_ALLCONFIG already does? It doesn't work 
for choices, but it's still fine for setting/clearing CONFIG_64BIT.

We'll want to make it simpler to use - so you really can do something like
   make CONFIG_64BIT=n randconfig
   make CONFIG_64BIT=n allmodconfig
   make CONFIG_64BIT=y CONFIG_SATA_MV=y oldconfig
etc. without having to create a text file. But that's not hard. A simple 
implementation might just *make* a file with the options on the command 
line and point KCONFIG_ALLCONFIG at it to start with, although there are 
probably cleaner ways to implement it.

And then this legacy trick of using the obsolete $ARCH settings to 
override the setting of CONFIG_64BIT can be deprecated.

-- 
dwmw2

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