linux-kernel - Re: [tip:x86/build] x86: Default to ARCH= x86 to avoid overriding CONFIG

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]

Date:	Sat, 12 Jan 2013 09:40:20 -0800
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Borislav Petkov <bp@...en8.de>,
	David Woodhouse <dwmw2@...radead.org>, mingo@...nel.org,
	linux-kernel@...r.kernel.org, tglx@...utronix.de,
	hpa@...ux.intel.com, David.Woodhouse@...el.com,
	linux-tip-commits@...r.kernel.org
Subject: Re: [tip:x86/build] x86: Default to ARCH= x86 to avoid overriding
 CONFIG_64BIT

On 01/12/2013 09:06 AM, Borislav Petkov wrote:
> 
> Ok, I don't know whether this was on purpose or not but setting ARCH=x86
> has the side effect of putting the config 64BIT prompt into the toplevel
> menuconfig:
> 
> 	[*] 64-bit kernel
> 	    General setup  --->
> 	[*] Enable loadable module support  --->
> 	[*] Enable the block layer  --->
> 	    Processor type and features  --->
> 
> Now, IMHO, maybe the more fitting place for this should be "Processor
> type and features" where all the arch-specific stuff goes but looking at
> arch/x86/Kconfig, it would need some restructuring due to dependencies.
> 
> So how about we simply hide it by still preserving the functionality:
> 

Hiding it because it happens to be in a slightly illogical place seems
completely backwards.

	-hpa


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