From: Peter Zijlstra <peterz@infradead.org>
To: Xin Li <xin@zytor.com>
Cc: linux-kernel@vger.kernel.org, luto@kernel.org,
tglx@linutronix.de, mingo@redhat.com, bp@alien8.de,
dave.hansen@linux.intel.com, x86@kernel.org, hpa@zytor.com,
jmill@asu.edu, andrew.cooper3@citrix.com
Subject: Re: [PATCH v1 1/1] x86/fred: Remove ENDBR64 from FRED entry points
Date: Tue, 15 Jul 2025 10:40:34 +0200 [thread overview]
Message-ID: <20250715084034.GO1613200@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <bb77f5f9-231a-4640-91b7-bca42e9654f3@zytor.com>
On Mon, Jul 14, 2025 at 11:50:57PM -0700, Xin Li wrote:
> On 7/14/2025 11:44 PM, Xin Li (Intel) wrote:
> > The FRED specification v9.0 states that there is no need for FRED
> > event handlers to begin with ENDBR64, because in the presence of
> > supervisor indirect branch tracking, FRED event delivery does not
> > enter the WAIT_FOR_ENDBRANCH state.
> >
> > As a result, remove ENDBR64 from FRED entry points.
> >
> > Then add ANNOTATE_NOENDBR to indicate that FRED entry points will
> > never be used for indirect calls to suppress an objtool warning.
> >
> > This change implies that any indirect CALL/JMP to FRED entry points
> > causes #CP in the presence of supervisor indirect branch tracking.
> >
> > Credit goes to Jennifer Miller <jmill@asu.edu> and other contributors
> > from Arizona State University whose work led to this change.
> >
> > Link: https://lore.kernel.org/linux-hardening/Z60NwR4w%2F28Z7XUa@ubun/
> > Reviewed-by: H. Peter Anvin (Intel) <hpa@zytor.com>
> > Signed-off-by: Xin Li (Intel) <xin@zytor.com>
> > Cc: Jennifer Miller <jmill@asu.edu>
> > Cc: Peter Zijlstra <peterz@infradead.org>
> > Cc: Andrew Cooper <andrew.cooper3@citrix.com>
> > Cc: H. Peter Anvin <hpa@zytor.com>
>
> Sorry, forgot to put CC stable.
Fixes: 14619d912b65 ("x86/fred: FRED entry/exit and dispatch code")
Right?
>
> > ---
> > arch/x86/entry/entry_64_fred.S | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/arch/x86/entry/entry_64_fred.S b/arch/x86/entry/entry_64_fred.S
> > index 29c5c32c16c3..907bd233c6c1 100644
> > --- a/arch/x86/entry/entry_64_fred.S
> > +++ b/arch/x86/entry/entry_64_fred.S
> > @@ -16,7 +16,7 @@
> > .macro FRED_ENTER
> > UNWIND_HINT_END_OF_STACK
> > - ENDBR
> > + ANNOTATE_NOENDBR
> > PUSH_AND_CLEAR_REGS
> > movq %rsp, %rdi /* %rdi -> pt_regs */
> > .endm
>
next prev parent reply other threads:[~2025-07-15 8:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-15 6:44 Xin Li (Intel)
2025-07-15 6:50 ` Xin Li
2025-07-15 8:40 ` Peter Zijlstra [this message]
2025-07-15 15:34 ` Xin Li
2025-07-15 15:49 ` Andrew Cooper
2025-07-15 16:10 ` Xin Li
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=20250715084034.GO1613200@noisy.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=andrew.cooper3@citrix.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=jmill@asu.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=xin@zytor.com \
/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®