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: <20110530105809.GA20133@elte.hu>
Date:	Mon, 30 May 2011 12:58:09 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Theodore Tso <tytso@....EDU>
Cc:	David Woodhouse <dwmw2@...radead.org>, x86@...nel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Fix corruption of CONFIG_X86_32 in 'make oldconfig'


* Theodore Tso <tytso@....EDU> wrote:

> I'd think that "make ARCH=x86_64 oldconfig"
> 
> ... where the old configuration contained CONFIG_X86_32
> should trigger a warning, if not an outright error that 
> stops the build....

That would be a rather sad regression for me: i use that command 
regularly to transform .configs that came in bugreports into a config 
suitable for a testbox that has a different bitness userspace 
installed.

Thanks,

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