linux-kernel - Re: [GIT pull] x86 mpx support for 3.19

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:	Wed, 10 Dec 2014 11:05:15 -0800
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Thomas Gleixner <tglx@...utronix.de>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	"the arch/x86 maintainers" <x86@...nel.org>,
	Dave Hansen <dave.hansen@...ux.intel.com>
Subject: Re: [GIT pull] x86 mpx support for 3.19

On Tue, Dec 9, 2014 at 6:08 AM, Thomas Gleixner <tglx@...utronix.de> wrote:
>
>    git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86-mpx-for-linus

So I've pulled this (not pushed out yet, I've done all the
allmodconfig builds, but I want to reboot into this all too), but I'm
not entirely sure I'm happy about how it enabled MPX support by
default.

Why would I want to enable this in my kernel when there are no actual
CPU's out yet that support it? And even when there are, why would I do
it if the CPU I have doesn't support it?

So I think it needs to be a real config option with a real question,
not a "def_bool" that just depends on "do you want to support Intel
CPU's"

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