linux-kernel - Re: [2.6 patch] x86: allow 64bit setting in Kconfig

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: <20080211163740.GA2446@elte.hu>
Date:	Mon, 11 Feb 2008 17:37:40 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Adrian Bunk <bunk@...nel.org>
Cc:	Sam Ravnborg <sam@...nborg.org>, tglx@...utronix.de,
	mingo@...hat.com, hpa@...or.com, linux-kernel@...r.kernel.org
Subject: Re: [2.6 patch] x86: allow 64bit setting in Kconfig


* Adrian Bunk <bunk@...nel.org> wrote:

> >     make ARCH=i386 randconfig
> > 
> > on a 64-bit box that has a 32-bit .config in its kernel directory.
> > 
> > The randconfig/allyesconfig/allnoconfig variants override whatever 
> > is in the current .config. Making the result depend on whatever is 
> > in the .config at the moment is fundamentally wrong.
> > 
> > "oldconfig" on the other hand has correct sensitivity to the 
> > existing .config - and that always worked correctly. So if you pop a 
> > 32-bit or a 64-bit .config into a kernel tree, that will be listened 
> > to, no matter whether you are on a 32-bit or on a 64-bit host.
> 
> Do you have ARCH=x86 set in your environment, the command line or 
> patched into your Makefile when this works for you?

nope, it happens with vanilla and no ARCH environment variable set that 
i know of. So you cannot see this behavior?

	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/