mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Borislav Petkov <bp@alien8.de>
Cc: "Masami Hiramatsu (Google)" <mhiramat@kernel.org>,
	Steven Rostedt <rostedt@goodmis.org>,
	Ingo Molnar <mingo@kernel.org>,
	Sean Christopherson <seanjc@google.com>,
	Jinchao Wang <wangjinchao600@gmail.com>,
	Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Dave Hansen <dave.hansen@linux.intel.com>,
	"H . Peter Anvin" <hpa@zytor.com>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	Ian Rogers <irogers@google.com>,
	linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
	linux-doc@vger.kernel.org, linux-perf-users@vger.kernel.org,
	x86@kernel.org, Paolo Bonzini <pbonzini@redhat.com>,
	kvm@vger.kernel.org
Subject: Re: [PATCH v17 01/13] x86/mce: Fix hardware debug register corruption on task migration
Date: Wed, 23 Sep 2026 10:46:21 +0200	[thread overview]
Message-ID: <20260923084621.GU776954@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <20260923002740.GAarMc_PJBsgo8Z-G9@fat_crate.local>

On Tue, Sep 22, 2026 at 05:27:40PM -0700, Borislav Petkov wrote:
> On Tue, Sep 22, 2026 at 01:24:55PM +0900, Masami Hiramatsu (Google) wrote:
> > From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
> > 
> > In exc_machine_check_user(), local_db_save() and local_db_restore() are
> > invoked in the outer entry stubs (DEFINE_IDTENTRY_MCE_USER,
> > DEFINE_FREDENTRY_MCE, and DEFINE_IDTENTRY_RAW), surrounding
> > exc_machine_check_user().
> > 
> > However, exc_machine_check_user() calls irqentry_exit_to_user_mode(),
> > which handles pending thread work and may schedule() if TIF_NEED_RESCHED
> > is set. If the task migrates to another CPU during schedule(),
> > local_db_restore() runs on the new CPU with the dr7 state saved from the
> > old CPU. This corrupts the new CPU's DR7 hardware debug register and
> > leaves the old CPU's DR7 disabled.
> > In short, local_db_save() and local_db_restore() pair must be run
> > on the same CPU.
> > 
> > To fix this, move local_db_save() and local_db_restore() inside
> > exc_machine_check_user() and exc_machine_check_kernel(). In
> > exc_machine_check_user(), DR7 is saved and restored strictly around
> > do_machine_check() to avoid schedule() during migration. In
> > exc_machine_check_kernel(), local_db_save() is called at the entry point
> > to prevent early memory accesses from triggering nested #DB exceptions,
> > and restored on all exits.
> > 
> > Fixes: cd840e424f27 ("x86/entry, mce: Disallow #DB during #MC")
> > Assisted-by: Antigravity:gemini-3.8-flash
> 
> verify_tags: WARNING: Zapping LLM ads tag: ['Antigravity:gemini-3.8-flash'].
> 
> Needs to be:
> 
> Assisted-by: LLM
> 
> Please fix all your patches.
> 
> > Signed-off-by: Masami Hiramatsu (Google) <mhiramat@kernel.org>
> > ---
> > Changes in v15:
> >  - Move local_db_save() to the entry of exc_machine_check_kernel() and
> >    restore it on early return from mce_check_crashing_cpu() to prevent
> >    nested #DB on watched variables.
> > Changes in v14:
> >  - Newly added.
> > ---
> >  arch/x86/kernel/cpu/mce/core.c |   27 ++++++++++-----------------
> >  1 file changed, 10 insertions(+), 17 deletions(-)
> 
> Yah, makes sense.
> 
> I'm thinking this needs to be CC:stable and I should take it in now.
> 
> Peter?

Yep is right.

Acked-by: Peter Zijlstra (Intel) <peterz@infradead.org>

  reply	other threads:[~2026-09-23  8:46 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-22  4:24 [PATCH v17 00/13] tracing: wprobe: x86: Add wprobe for watchpoint Masami Hiramatsu (Google)
2026-09-22  4:24 ` [PATCH v17 01/13] x86/mce: Fix hardware debug register corruption on task migration Masami Hiramatsu (Google)
2026-09-23  0:27   ` Borislav Petkov
2026-09-23  8:46     ` Peter Zijlstra [this message]
2026-09-23  8:56     ` Masami Hiramatsu
2026-09-23 18:36   ` [tip: x86/urgent] " tip-bot2 for Masami Hiramatsu (Google)
2026-09-22  4:25 ` [PATCH v17 02/13] perf/x86, KVM: Prevent host debug register leak into guest OS on NMI Masami Hiramatsu (Google)
2026-09-23  8:51   ` Peter Zijlstra
2026-09-23 14:33     ` Sean Christopherson
2026-09-23  9:15   ` Peter Zijlstra
2026-09-23 15:32     ` Sean Christopherson
2026-09-24  0:56       ` Masami Hiramatsu
2026-09-22  4:25 ` [PATCH v17 03/13] x86/hw_breakpoints: Make DR7 updates NMI safe Masami Hiramatsu (Google)
2026-09-23  9:13   ` Peter Zijlstra
2026-09-22  4:25 ` [PATCH v17 04/13] x86/hw_breakpoints: Add arch_modify_local_hw_breakpoint_addr() API Masami Hiramatsu (Google)
2026-09-22  4:25 ` [PATCH v17 05/13] HWBP: Add modify_local_hw_breakpoint_addr() API Masami Hiramatsu (Google)
2026-09-22  4:25 ` [PATCH v17 06/13] tracing/wprobe: Add wprobe (watchpoint probe) trace event support Masami Hiramatsu (Google)
2026-09-22  4:26 ` [PATCH v17 07/13] x86: hw_breakpoint: Add a kconfig to clarify when a breakpoint fires Masami Hiramatsu (Google)
2026-09-22  4:26 ` [PATCH v17 08/13] selftests: tracing: Add a basic testcase for wprobe Masami Hiramatsu (Google)
2026-09-22  4:26 ` [PATCH v17 09/13] selftests: tracing: Add syntax " Masami Hiramatsu (Google)
2026-09-22  4:26 ` [PATCH v17 10/13] tracing/wprobe: Add set_wprobe and clear_wprobe event triggers Masami Hiramatsu (Google)
2026-09-22  4:26 ` [PATCH v17 11/13] selftests: tracing: Add wprobe trigger testcases Masami Hiramatsu (Google)
2026-09-22  4:27 ` [PATCH v17 12/13] tracing/wprobe: Support BTF typecast in fetchargs Masami Hiramatsu (Google)
2026-09-22  4:27 ` [PATCH v17 13/13] tracing/wprobe: Support BTF struct offset resolution in set_wprobe trigger Masami Hiramatsu (Google)

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=20260923084621.GU776954@noisy.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=irogers@google.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=mhiramat@kernel.org \
    --cc=mingo@kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=rostedt@goodmis.org \
    --cc=seanjc@google.com \
    --cc=tglx@linutronix.de \
    --cc=wangjinchao600@gmail.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

all inboxes | Powered by JetHome®