From: Andy Lutomirski <luto@kernel.org>
To: x86@kernel.org
Cc: Sasha Levin <sasha.levin@oracle.com>,
linux-kernel@vger.kernel.org, Andy Lutomirski <luto@kernel.org>,
stable@vger.kernel.org
Subject: [PATCH 2/2] x86/nmi/64: Fix a paravirt stack-clobbering bug in the NMI code
Date: Sun, 20 Sep 2015 16:32:05 -0700 [thread overview]
Message-ID: <974bc40edffdb5c2950a5c4977f821a446b76178.1442791737.git.luto@kernel.org> (raw)
In-Reply-To: <cover.1442791737.git.luto@kernel.org>
In-Reply-To: <cover.1442791737.git.luto@kernel.org>
The NMI entry code that switches to the normal kernel stack needs to
be very careful not to clobber any extra stack slots on the NMI
stack. The code is fine under the assumption that SWAPGS is just a
normal instruction, but that assumption isn't really true. Use
SWAPGS_UNSAFE_STACK instead.
This is part of a fix for some random crashes that Sasha saw.
Fixes: 9b6e6a8334d5 ("x86/nmi/64: Switch stacks on userspace NMI entry")
Cc: stable@vger.kernel.org
Reported-and-tested-by: Sasha Levin <sasha.levin@oracle.com>
Signed-off-by: Andy Lutomirski <luto@kernel.org>
---
arch/x86/entry/entry_64.S | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/arch/x86/entry/entry_64.S b/arch/x86/entry/entry_64.S
index f7492133a7bb..2c61e8070ba4 100644
--- a/arch/x86/entry/entry_64.S
+++ b/arch/x86/entry/entry_64.S
@@ -1205,9 +1205,12 @@ ENTRY(nmi)
* we don't want to enable interrupts, because then we'll end
* up in an awkward situation in which IRQs are on but NMIs
* are off.
+ *
+ * We also must not push anything to the stack before switching
+ * stacks lest we corrupt the "NMI executing" variable.
*/
- SWAPGS
+ SWAPGS_UNSAFE_STACK
cld
movq %rsp, %rdx
movq PER_CPU_VAR(cpu_current_top_of_stack), %rsp
--
2.4.3
next prev parent reply other threads:[~2015-09-20 23:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-20 23:32 [PATCH 0/2] x86: NMI vs paravirt fixes Andy Lutomirski
2015-09-20 23:32 ` [PATCH 1/2] x86/paravirt: Replace the paravirt nop with a bona fide empty function Andy Lutomirski
2015-09-22 19:48 ` [tip:x86/urgent] " tip-bot for Andy Lutomirski
2015-09-22 20:42 ` tip-bot for Andy Lutomirski
2015-09-20 23:32 ` Andy Lutomirski [this message]
2015-09-22 19:48 ` [tip:x86/urgent] x86/nmi/64: Fix a paravirt stack-clobbering bug in the NMI code tip-bot for Andy Lutomirski
2015-09-22 20:42 ` tip-bot for Andy Lutomirski
2015-09-21 19:14 ` [PATCH 0/2] x86: NMI vs paravirt fixes Andy Lutomirski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=974bc40edffdb5c2950a5c4977f821a446b76178.1442791737.git.luto@kernel.org \
--to=luto@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sasha.levin@oracle.com \
--cc=stable@vger.kernel.org \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®