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: <20110530121137.GF22324@elte.hu>
Date:	Mon, 30 May 2011 14:11:37 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	David Woodhouse <dwmw2@...radead.org>
Cc:	x86@...nel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Fix corruption of CONFIG_X86_32 in 'make oldconfig'


* David Woodhouse <dwmw2@...radead.org> wrote:

> On Mon, 30 May 2011, Ingo Molnar wrote:
> 
> > 
> > What kind of replacement are you suggesting?
> 
> I suspect that
>     make CONFIG_64BIT=y CONFIG_SATA_MV=y whateverconfig
> 
> ought to work for all the examples shown so far?

Well, some people will argue that:

	make ARCH=i386 whateverconfig

is less typing than:

	make CONFIG_64BIT=y whateverconfig                 # set bitness
	make CONFIG_64BIT=y ARCH=x86 whateverconfig        # set architecture and bitness

but yes, in the long run i agree that 'ARCH=i386' would simply be a 
(legacy) shortcut for:
 
        CONFIG_64BIT=y ARCH=x86

and 'ARCH=x86_64' should be a (legacy) shortcut for:

        CONFIG_64BIT=n ARCH=x86

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/