From: Peter Zijlstra <peterz@infradead.org>
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: LKML <linux-kernel@vger.kernel.org>, Alex Zenla <alex@edera.dev>,
Josh Poimboeuf <jpoimboe@kernel.org>,
Jason Baron <jbaron@akamai.com>,
Steven Rostedt <rostedt@goodmis.org>,
Ard Biesheuvel <ardb@kernel.org>,
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>,
Juergen Gross <jgross@suse.com>,
stable@kernel.org
Subject: Re: [PATCH] x86/static-call: Remove early_boot_irqs_disabled check to fix Xen PVH dom0
Date: Sun, 22 Dec 2024 12:03:05 +0100 [thread overview]
Message-ID: <20241222110305.GR11133@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <20241221211046.6475-1-andrew.cooper3@citrix.com>
On Sat, Dec 21, 2024 at 09:10:46PM +0000, Andrew Cooper wrote:
> __static_call_update_early() has a check for early_boot_irqs_disabled, but
> is used before early_boot_irqs_disabled is set up in start_kernel().
>
> Xen PV has always special cased early_boot_irqs_disabled, but Xen PVH does
> not and falls over the BUG when booting as dom0.
>
> It is very suspect that early_boot_irqs_disabled starts as 0, becomes 1 for
> a time, then becomes 0 again, but as this needs backporting to fix a
> breakage in a security fix, dropping the BUG_ON() is the far safer option.
Agreed.
> Fixes: 0ef8047b737d ("x86/static-call: provide a way to do very early static-call updates")
> Reported-by: Alex Zenla <alex@edera.dev>
> Closes: https://bugzilla.kernel.org/show_bug.cgi?id=219620
> Suggested-by: Peter Zijlstra <peterz@infradead.org>
> Tested-by: Alex Zenla <alex@edera.dev>
> Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
Acked-by: Peter Zijlstra (Intel) <peterz@infradead.org>
> ---
> arch/x86/kernel/static_call.c | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/arch/x86/kernel/static_call.c b/arch/x86/kernel/static_call.c
> index 9eed0c144dad..9e51242ed125 100644
> --- a/arch/x86/kernel/static_call.c
> +++ b/arch/x86/kernel/static_call.c
> @@ -175,7 +175,6 @@ EXPORT_SYMBOL_GPL(arch_static_call_transform);
> noinstr void __static_call_update_early(void *tramp, void *func)
> {
> BUG_ON(system_state != SYSTEM_BOOTING);
> - BUG_ON(!early_boot_irqs_disabled);
> BUG_ON(static_call_initialized);
> __text_gen_insn(tramp, JMP32_INSN_OPCODE, tramp, func, JMP32_INSN_SIZE);
> sync_core();
>
> base-commit: e84a3bf7f4aa669c05e3884497774148ac111468
> --
> 2.39.5
>
next prev parent reply other threads:[~2024-12-22 11:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-21 21:10 [PATCH] x86/static-call: Remove early_boot_irqs_disabled check to fix Xen PVH dom0 Andrew Cooper
2024-12-22 11:03 ` Peter Zijlstra [this message]
2025-01-02 11:57 ` Jürgen Groß
2025-01-02 16:30 ` [tip: x86/urgent] " tip-bot2 for Andrew Cooper
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=20241222110305.GR11133@noisy.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=alex@edera.dev \
--cc=andrew.cooper3@citrix.com \
--cc=ardb@kernel.org \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=jbaron@akamai.com \
--cc=jgross@suse.com \
--cc=jpoimboe@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.org \
--cc=stable@kernel.org \
--cc=tglx@linutronix.de \
--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