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: <alpine.LFD.2.02.1105301955210.3164@localhost6.localdomain6>
Date:	Mon, 30 May 2011 20:03:08 +0100 (BST)
From:	David Woodhouse <dwmw2@...radead.org>
To:	Theodore Tso <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, Theodore Tso wrote:
> All this talk of how it's OK for randconfig to give you i386 50% of the time
> even when ARCH=x86_64 is specified is confusing me?  Maybe that
> was just intended to be sarcasm?

No, I don't believe that was ever actually said at all. Certainly not this 
year.

What was said was that with ARCH=x86, it's OK for randconfig to be random.

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.

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