From: Sean Christopherson <seanjc@google.com>
To: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
linux-kernel@vger.kernel.org,
"Guilherme G . Piccoli" <gpiccoli@igalia.com>,
Vitaly Kuznetsov <vkuznets@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [PATCH v2 0/3] x86/crash: Fix double NMI shootdown bug
Date: Fri, 8 Jul 2022 23:28:37 +0000 [thread overview]
Message-ID: <Ysi9pVFHsqM3uivr@google.com> (raw)
In-Reply-To: <20220518001647.1291448-1-seanjc@google.com>
On Wed, May 18, 2022, Sean Christopherson wrote:
> Fix a double NMI shootdown bug found and debugged by Guilherme, who did all
> the hard work. NMI shootdown is a one-time thing; the handler leaves NMIs
> blocked and enters halt. At best, a second (or third...) shootdown is an
> expensive nop, at worst it can hang the kernel and prevent kexec'ing into
> a new kernel, e.g. prior to the hardening of register_nmi_handler(), a
> double shootdown resulted in a double list_add(), which is fatal when running
> with CONFIG_BUG_ON_DATA_CORRUPTION=y.
...
> Sean Christopherson (3):
> x86/crash: Disable virt in core NMI crash handler to avoid double
> shootdown
> x86/reboot: Disable virtualization in an emergency if SVM is supported
> x86/virt: Fold __cpu_emergency_vmxoff() into its sole caller
>
> arch/x86/include/asm/reboot.h | 1 +
> arch/x86/include/asm/virtext.h | 14 +-----
> arch/x86/kernel/crash.c | 16 +-----
> arch/x86/kernel/reboot.c | 89 +++++++++++++++++++++++++---------
> 4 files changed, 69 insertions(+), 51 deletions(-)
Ping! Still applies cleanly.
next prev parent reply other threads:[~2022-07-08 23:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-18 0:16 [PATCH v2 0/3] x86/crash: Fix double NMI shootdown bug Sean Christopherson
2022-05-18 0:16 ` [PATCH v2 1/3] x86/crash: Disable virt in core NMI crash handler to avoid double shootdown Sean Christopherson
2022-05-18 15:50 ` Guilherme G. Piccoli
2022-05-18 0:16 ` [PATCH v2 2/3] x86/reboot: Disable virtualization in an emergency if SVM is supported Sean Christopherson
2022-05-18 0:16 ` [PATCH v2 3/3] x86/virt: Fold __cpu_emergency_vmxoff() into its sole caller Sean Christopherson
2022-06-03 16:07 ` [PATCH v2 0/3] x86/crash: Fix double NMI shootdown bug Guilherme G. Piccoli
2022-07-08 23:28 ` Sean Christopherson [this message]
2022-08-22 18:39 ` Guilherme G. Piccoli
2022-10-03 16:03 ` Guilherme G. Piccoli
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=Ysi9pVFHsqM3uivr@google.com \
--to=seanjc@google.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=gpiccoli@igalia.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=tglx@linutronix.de \
--cc=vkuznets@redhat.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