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>
Subject: [PATCH 0/2] x86: NMI vs paravirt fixes
Date: Sun, 20 Sep 2015 16:32:03 -0700 [thread overview]
Message-ID: <cover.1442791737.git.luto@kernel.org> (raw)
These are for x86/urgent.
This fixes at least one problem that Sasha can trigger using some
crazy configuration + Trinity. I can't reproduce the full file of
nastiness that he's seeing, but these patches both look legit to me,
they fix what look like real bugs, and they seem to help Sasha's
tests.
Patch 1 is ugly. Feel free to tell me to shove the asm into the
entry asm files, although that will involve duplicating it for
32-bit and 64-bit kernels.
Andy Lutomirski (2):
x86/paravirt: Replace the paravirt nop with a bona fide empty function
x86/nmi/64: Fix a paravirt stack-clobbering bug in the NMI code
arch/x86/entry/entry_64.S | 16 +++++++++++++++-
arch/x86/kernel/paravirt.c | 16 ++++++++++++----
2 files changed, 27 insertions(+), 5 deletions(-)
--
2.4.3
next 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 Andy Lutomirski [this message]
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 ` [PATCH 2/2] x86/nmi/64: Fix a paravirt stack-clobbering bug in the NMI code 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-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=cover.1442791737.git.luto@kernel.org \
--to=luto@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sasha.levin@oracle.com \
--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