From: Peter Zijlstra <peterz@infradead.org>
To: Menglong Dong <menglong8.dong@gmail.com>
Cc: rostedt@goodmis.org, mark.rutland@arm.com,
alexei.starovoitov@gmail.com, catalin.marinas@arm.com,
will@kernel.org, mhiramat@kernel.org, tglx@linutronix.de,
mingo@redhat.com, bp@alien8.de, dave.hansen@linux.intel.com,
x86@kernel.org, hpa@zytor.com, ast@kernel.org,
daniel@iogearbox.net, andrii@kernel.org, martin.lau@linux.dev,
eddyz87@gmail.com, yonghong.song@linux.dev,
john.fastabend@gmail.com, kpsingh@kernel.org, sdf@fomichev.me,
jolsa@kernel.org, davem@davemloft.net, dsahern@kernel.org,
mathieu.desnoyers@efficios.com, nathan@kernel.org,
nick.desaulniers+lkml@gmail.com, morbo@google.com,
samitolvanen@google.com, kees@kernel.org,
dongml2@chinatelecom.cn, akpm@linux-foundation.org,
riel@surriel.com, rppt@kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
bpf@vger.kernel.org, netdev@vger.kernel.org,
llvm@lists.linux.dev
Subject: Re: [PATCH bpf-next v3 1/4] x86/ibt: factor out cfi and fineibt offset
Date: Mon, 3 Mar 2025 12:24:48 +0100 [thread overview]
Message-ID: <20250303112448.GZ11590@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <CADxym3as+KdeBMUigq4xq302g2U7UG-7Gm+vKiYGnSjHouq=bg@mail.gmail.com>
On Mon, Mar 03, 2025 at 06:51:41PM +0800, Menglong Dong wrote:
> On Mon, Mar 3, 2025 at 5:18 PM Peter Zijlstra <peterz@infradead.org> wrote:
> >
> > On Mon, Mar 03, 2025 at 02:53:42PM +0800, Menglong Dong wrote:
> > > index c71b575bf229..ad050d09cb2b 100644
> > > --- a/arch/x86/kernel/alternative.c
> > > +++ b/arch/x86/kernel/alternative.c
> > > @@ -908,7 +908,7 @@ void __init_or_module noinline apply_seal_endbr(s32 *start, s32 *end, struct mod
> > >
> > > poison_endbr(addr, wr_addr, true);
> > > if (IS_ENABLED(CONFIG_FINEIBT))
> > > - poison_cfi(addr - 16, wr_addr - 16);
> > > + poison_cfi(addr, wr_addr);
> > > }
> > > }
> >
> > If you're touching this code, please use tip/x86/core or tip/master.
>
> Thank you for reminding me that, I were using the linux-next, and
That must've been an very old -next, because that wr_addr crap has been
gone a while now.
Anyway, thanks for moving to a newer tree!
next prev parent reply other threads:[~2025-03-03 11:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-03 6:53 [PATCH bpf-next v3 0/4] per-function storage support Menglong Dong
2025-03-03 6:53 ` [PATCH bpf-next v3 1/4] x86/ibt: factor out cfi and fineibt offset Menglong Dong
2025-03-03 9:18 ` Peter Zijlstra
2025-03-03 10:51 ` Menglong Dong
2025-03-03 11:24 ` Peter Zijlstra [this message]
2025-03-03 6:53 ` [PATCH bpf-next v3 2/4] add per-function metadata storage support Menglong Dong
2025-03-03 6:53 ` [PATCH bpf-next v3 3/4] x86: implement per-function metadata storage for x86 Menglong Dong
2025-03-03 16:05 ` Steven Rostedt
2025-03-04 2:07 ` Menglong Dong
2025-03-04 3:06 ` Menglong Dong
2025-03-03 6:53 ` [PATCH bpf-next v3 4/4] arm64: implement per-function metadata storage for arm64 Menglong Dong
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=20250303112448.GZ11590@noisy.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=alexei.starovoitov@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bp@alien8.de \
--cc=bpf@vger.kernel.org \
--cc=catalin.marinas@arm.com \
--cc=daniel@iogearbox.net \
--cc=dave.hansen@linux.intel.com \
--cc=davem@davemloft.net \
--cc=dongml2@chinatelecom.cn \
--cc=dsahern@kernel.org \
--cc=eddyz87@gmail.com \
--cc=hpa@zytor.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kees@kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=mark.rutland@arm.com \
--cc=martin.lau@linux.dev \
--cc=mathieu.desnoyers@efficios.com \
--cc=menglong8.dong@gmail.com \
--cc=mhiramat@kernel.org \
--cc=mingo@redhat.com \
--cc=morbo@google.com \
--cc=nathan@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nick.desaulniers+lkml@gmail.com \
--cc=riel@surriel.com \
--cc=rostedt@goodmis.org \
--cc=rppt@kernel.org \
--cc=samitolvanen@google.com \
--cc=sdf@fomichev.me \
--cc=tglx@linutronix.de \
--cc=will@kernel.org \
--cc=x86@kernel.org \
--cc=yonghong.song@linux.dev \
/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