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]

Message-ID: <20110530195545.GG2890@dhcp-172-31-194-241.cam.corp.google.com>
Date:	Mon, 30 May 2011 15:55:45 -0400
From:	Ted Ts'o <tytso@....edu>
To:	David Woodhouse <dwmw2@...radead.org>
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, May 30, 2011 at 08:03:08PM +0100, David Woodhouse wrote:
> 
> And that the legacy trick of using ARCH=i386 or ARCH=x86_64 as a hack to 
> override *just* CONFOG_64BIT, although nobody has posted a patch which 
> removes or breaks that, probably ought to be deprecated in favour of a 
> more generic way to override config options - one that doesn't work only 
> for *one* config option, and only on *one* architecture.

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.

The other way would be some kind of new tagging in the .config file
itself, e.g.:

CONFIG_64BIT=y	# FIXED

There are all sorts of interesting design questions hidden in here, of
course, including what if the fixedpoint declarations (whether done
via a separate file or via tags in .config) are mutually inconsistent.

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