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: <20110531125019.GB10249@elte.hu>
Date:	Tue, 31 May 2011 14:50:19 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Ted Ts'o <tytso@....edu>, David Woodhouse <dwmw2@...radead.org>,
	x86@...nel.org, linux-kernel@...r.kernel.org,
	Alexey Dobriyan <adobriyan@...il.com>,
	Randy Dunlap <rdunlap@...otime.net>
Subject: Re: [PATCH] Fix corruption of CONFIG_X86_32 in 'make oldconfig'


* Ted Ts'o <tytso@....edu> wrote:

> On Tue, May 31, 2011 at 09:55:47AM +0100, David Woodhouse wrote:
> > On Tue, 2011-05-31 at 09:53 +0200, Ingo Molnar wrote:
> > > I'll always prefer typing:
> > >   make ARCH=x86_64 ...
> > > To:
> > >   make ARCH=x86 CONFIG_64BIT=y ...
> > 
> > You're not building on an x86 box? I always suspected you had some alien
> > technology! Does it run Linux?
> > 
> > Why else would you need to specify ARCH=x86 on the latter command line? 
> 
> I don't know why Ingo needs ARCH=x86 on the command line, [...]

I replied to the hypothetical scenario where CONFIG_64BIT=y works and 
ARCH=x86_64 and ARCH=i386 are deprecated because they are supposedly 
a 'dirty hack' and 'obsolete'. (David's words, not mine)

I vehemently disagree with the deprecation of ARCH=i386 and 
ARCH=x86_64 and with the characterisation as well.

> [...] but I regularly type "make ARCH=i386" when building 32-bit 
> kernels on a 64-bit system, and my scripts use "make ARCH=x86_64" 
> when building 64-bit kernels (just in case I happen to have booted 
> a 32-bit kernel).

Ditto here. They are not just useful but logical as well. This is 
what the whole thread is about: i want this behavior to be 
*preserved*.

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/