From: Peter Zijlstra <peterz@infradead.org>
To: x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>
Cc: kees@kernel.org, alyssa.milburn@intel.com,
scott.d.constable@intel.com, joao@overdrivepizza.com,
andrew.cooper3@citrix.com, samitolvanen@google.com,
nathan@kernel.org, alexei.starovoitov@gmail.com,
mhiramat@kernel.org, ojeda@kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [RFC][PATCH] x86,ibt: Use UDB instead of 0xEA
Date: Thu, 14 Aug 2025 13:23:28 +0200 [thread overview]
Message-ID: <20250814112328.GC4068168@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <20250814111732.GW4067720@noisy.programming.kicks-ass.net>
On Thu, Aug 14, 2025 at 01:17:33PM +0200, Peter Zijlstra wrote:
> diff --git a/arch/x86/kernel/cet.c b/arch/x86/kernel/cet.c
> index 99444409c026..59f8bf022ec5 100644
> --- a/arch/x86/kernel/cet.c
> +++ b/arch/x86/kernel/cet.c
> @@ -123,7 +123,7 @@ static void do_kernel_cp_fault(struct pt_regs *regs, unsigned long error_code)
> return;
> }
>
> - pr_err("Missing ENDBR: %pS\n", (void *)instruction_pointer(regs));
> + early_printk("Missing ENDBR: %pS\n", (void *)instruction_pointer(regs));
> if (!ibt_fatal) {
> printk(KERN_DEFAULT CUT_HERE);
> __warn(__FILE__, __LINE__, (void *)regs->ip, TAINT_WARN, regs, NULL);
Obviously this is debugging remnant and will go away.
next prev parent reply other threads:[~2025-08-14 11:23 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-14 11:17 [RFC][PATCH] x86,ibt: Use UDB instead of 0xEA Peter Zijlstra
2025-08-14 11:23 ` Peter Zijlstra [this message]
2025-08-14 19:40 ` Nathan Chancellor
2025-08-15 1:27 ` H. Peter Anvin
2025-08-15 7:49 ` Peter Zijlstra
2025-08-15 10:28 ` Peter Zijlstra
2025-08-15 10:30 ` Peter Zijlstra
2025-08-15 10:43 ` Andrew Cooper
2025-08-15 10:59 ` Peter Zijlstra
2025-08-15 11:19 ` Andrew Cooper
2025-08-15 17:14 ` H. Peter Anvin
2025-08-15 17:21 ` Andrew Cooper
2025-08-15 17:28 ` H. Peter Anvin
2025-08-15 5:42 ` Alexei Starovoitov
2025-08-15 7:57 ` Peter Zijlstra
2025-08-15 8:28 ` Leon Hwang
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=20250814112328.GC4068168@noisy.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=alexei.starovoitov@gmail.com \
--cc=alyssa.milburn@intel.com \
--cc=andrew.cooper3@citrix.com \
--cc=hpa@zytor.com \
--cc=joao@overdrivepizza.com \
--cc=kees@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=nathan@kernel.org \
--cc=ojeda@kernel.org \
--cc=samitolvanen@google.com \
--cc=scott.d.constable@intel.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