linux-kernel - [tip:x86/urgent] x86/cpu: Fix SMAP check in PVOPS environments

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] [day] [month] [year] [list]

Message-ID: <tip-581b7f158fe0383b492acd1ce3fb4e99d4e57808@git.kernel.org>
Date:	Thu, 19 Nov 2015 02:12:51 -0800
From:	tip-bot for Andrew Cooper <tipbot@...or.com>
To:	linux-tip-commits@...r.kernel.org
Cc:	rusty@...tcorp.com.au, linux-kernel@...r.kernel.org,
	mingo@...nel.org, david.vrabel@...rix.com, tglx@...utronix.de,
	xen-devel@...ts.xen.org, boris.ostrovsky@...cle.com, hpa@...or.com,
	lguest@...ts.ozlabs.org, konrad.wilk@...cle.com,
	andrew.cooper3@...rix.com
Subject: [tip:x86/urgent] x86/cpu: Fix SMAP check in PVOPS environments

Commit-ID:  581b7f158fe0383b492acd1ce3fb4e99d4e57808
Gitweb:     http://git.kernel.org/tip/581b7f158fe0383b492acd1ce3fb4e99d4e57808
Author:     Andrew Cooper <andrew.cooper3@...rix.com>
AuthorDate: Wed, 3 Jun 2015 10:31:14 +0100
Committer:  Thomas Gleixner <tglx@...utronix.de>
CommitDate: Thu, 19 Nov 2015 11:07:49 +0100

x86/cpu: Fix SMAP check in PVOPS environments

There appears to be no formal statement of what pv_irq_ops.save_fl() is
supposed to return precisely.  Native returns the full flags, while lguest and
Xen only return the Interrupt Flag, and both have comments by the
implementations stating that only the Interrupt Flag is looked at.  This may
have been true when initially implemented, but no longer is.

To make matters worse, the Xen PVOP leaves the upper bits undefined, making
the BUG_ON() undefined behaviour.  Experimentally, this now trips for 32bit PV
guests on Broadwell hardware.  The BUG_ON() is consistent for an individual
build, but not consistent for all builds.  It has also been a sitting timebomb
since SMAP support was introduced.

Use native_save_fl() instead, which will obtain an accurate view of the AC
flag.

Signed-off-by: Andrew Cooper <andrew.cooper3@...rix.com>
Reviewed-by: David Vrabel <david.vrabel@...rix.com>
Tested-by: Rusty Russell <rusty@...tcorp.com.au>
Cc: Rusty Russell <rusty@...tcorp.com.au>
Cc: Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>
Cc: Boris Ostrovsky <boris.ostrovsky@...cle.com>
Cc: <lguest@...ts.ozlabs.org>
Cc: Xen-devel <xen-devel@...ts.xen.org>
CC: stable@...r.kernel.org
Link: http://lkml.kernel.org/r/1433323874-6927-1-git-send-email-andrew.cooper3@citrix.com
Signed-off-by: Thomas Gleixner <tglx@...utronix.de>
---
 arch/x86/kernel/cpu/common.c | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/arch/x86/kernel/cpu/common.c b/arch/x86/kernel/cpu/common.c
index 4ddd780..c2b7522 100644
--- a/arch/x86/kernel/cpu/common.c
+++ b/arch/x86/kernel/cpu/common.c
@@ -273,10 +273,9 @@ __setup("nosmap", setup_disable_smap);
 
 static __always_inline void setup_smap(struct cpuinfo_x86 *c)
 {
-	unsigned long eflags;
+	unsigned long eflags = native_save_fl();
 
 	/* This should have been cleared long ago */
-	raw_local_save_flags(eflags);
 	BUG_ON(eflags & X86_EFLAGS_AC);
 
 	if (cpu_has(c, X86_FEATURE_SMAP)) {
--
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/