From: patchwork-bot+netdevbpf@kernel.org
To: Xu Kuohai <xukuohai@huaweicloud.com>
Cc: bpf@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, ast@kernel.org,
daniel@iogearbox.net, andrii@kernel.org, martin.lau@linux.dev,
eddyz87@gmail.com, memxor@gmail.com, yonghong.song@linux.dev,
puranjay@kernel.org, a.s.protopopov@gmail.com,
alexis.lothore@bootlin.com, list+bpf@vahedi.org,
linux@armlinux.org.uk, yangtiezhu@loongson.cn,
hengqi.chen@gmail.com, johan.almbladh@anyfinetworks.com,
paulburton@kernel.org, hbathini@linux.ibm.com,
chleroy@kernel.org, naveen@kernel.org, luke.r.nels@gmail.com,
xi.wang@gmail.com, bjorn@kernel.org, pulehui@huawei.com,
iii@linux.ibm.com, hca@linux.ibm.com, gor@linux.ibm.com,
davem@davemloft.net, udknight@gmail.com
Subject: Re: [PATCH bpf v15 0/5] emit ENDBR/BTI instructions for indirect
Date: Thu, 16 Apr 2026 14:10:13 +0000 [thread overview]
Message-ID: <177634861305.3246567.7251798812226371156.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260416064341.151802-1-xukuohai@huaweicloud.com>
Hello:
This series was applied to bpf/bpf.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Thu, 16 Apr 2026 06:43:36 +0000 you wrote:
> On architectures with CFI protection enabled that require landing pad
> instructions at indirect jump targets, such as x86 with CET/IBT enabled
> and arm64 with BTI enabled, kernel panics when an indirect jump lands on
> a target without landing pad. Therefore, the JIT must emit landing pad
> instructions for indirect jump targets.
>
> The verifier already recognizes which instructions are indirect jump
> targets during the verification phase. So we can store this information
> in env->insn_aux_data and pass it to the JIT as new parameter, allowing
> the JIT to consult env->insn_aux_data to determine which instructions are
> indirect jump targets.
>
> [...]
Here is the summary with links:
- [bpf,v15,1/5] bpf: Move constants blinding out of arch-specific JITs
https://git.kernel.org/bpf/bpf/c/d3e945223e01
- [bpf,v15,2/5] bpf: Pass bpf_verifier_env to JIT
https://git.kernel.org/bpf/bpf/c/d9ef13f72711
- [bpf,v15,3/5] bpf: Add helper to detect indirect jump targets
https://git.kernel.org/bpf/bpf/c/07ae6c130b46
- [bpf,v15,4/5] bpf, x86: Emit ENDBR for indirect jump targets
https://git.kernel.org/bpf/bpf/c/9a0e89dcc9be
- [bpf,v15,5/5] bpf, arm64: Emit BTI for indirect jump target
https://git.kernel.org/bpf/bpf/c/f6606a44bc43
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-04-16 14:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-16 6:43 [PATCH bpf v15 0/5] emit ENDBR/BTI instructions for indirect Xu Kuohai
2026-04-16 6:43 ` [PATCH bpf v15 1/5] bpf: Move constants blinding out of arch-specific JITs Xu Kuohai
2026-04-16 6:43 ` [PATCH bpf v15 2/5] bpf: Pass bpf_verifier_env to JIT Xu Kuohai
2026-04-16 6:43 ` [PATCH bpf v15 3/5] bpf: Add helper to detect indirect jump targets Xu Kuohai
2026-04-16 6:43 ` [PATCH bpf v15 4/5] bpf, x86: Emit ENDBR for " Xu Kuohai
2026-04-16 6:43 ` [PATCH bpf v15 5/5] bpf, arm64: Emit BTI for indirect jump target Xu Kuohai
2026-04-16 14:10 ` patchwork-bot+netdevbpf [this message]
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=177634861305.3246567.7251798812226371156.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=a.s.protopopov@gmail.com \
--cc=alexis.lothore@bootlin.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bjorn@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=chleroy@kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=eddyz87@gmail.com \
--cc=gor@linux.ibm.com \
--cc=hbathini@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=hengqi.chen@gmail.com \
--cc=iii@linux.ibm.com \
--cc=johan.almbladh@anyfinetworks.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=list+bpf@vahedi.org \
--cc=luke.r.nels@gmail.com \
--cc=martin.lau@linux.dev \
--cc=memxor@gmail.com \
--cc=naveen@kernel.org \
--cc=paulburton@kernel.org \
--cc=pulehui@huawei.com \
--cc=puranjay@kernel.org \
--cc=udknight@gmail.com \
--cc=xi.wang@gmail.com \
--cc=xukuohai@huaweicloud.com \
--cc=yangtiezhu@loongson.cn \
--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