linux-kernel - Re: [PATCH] [RFC] x86: work around MPX Erratum

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: <20160503214535.GW27540@pd.tnic>
Date:	Tue, 3 May 2016 23:45:35 +0200
From:	Borislav Petkov <bp@...en8.de>
To:	Dave Hansen <dave.hansen@...el.com>
Cc:	Ingo Molnar <mingo@...nel.org>, linux-kernel@...r.kernel.org,
	x86@...nel.org, Andy Lutomirski <luto@...nel.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	"H. Peter Anvin" <hpa@...or.com>,
	Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: [PATCH] [RFC] x86: work around MPX Erratum

On Tue, May 03, 2016 at 02:28:18PM -0700, Dave Hansen wrote:
> Generally, I'm not sure we need the no$foo options at all.  There's
> always "clearcpuid=" which does the same thing.  It just requires you to
> go look up the X86_FEATURE_* bit first.

Yeah, the "no-" things are all chicken bits which we should get rid of
at some point anyway.

> What do you mean by disable? Have qemu error out if MPX and SMEP
> aren't disabled in concert with each other?

Yap.

-- 
Regards/Gruss,
    Boris.

ECO tip #101: Trim your mails when you reply.