From: patchwork-bot+netdevbpf@kernel.org
To: Leon Hwang <leon.hwang@linux.dev>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
john.fastabend@gmail.com, andrii@kernel.org, eddyz87@gmail.com,
memxor@gmail.com, martin.lau@linux.dev, song@kernel.org,
yonghong.song@linux.dev, jolsa@kernel.org, emil@etsalapatis.com,
shuah@kernel.org, tanjingguo@huawei.com, pulehui@huawei.com,
malin89@huawei.com, maciej.fijalkowski@intel.com,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
kernel-patches-bot@fb.com
Subject: Re: [PATCH bpf-next v2 0/2] bpf: Fix WARNING in bpf_tracing_link_release
Date: Fri, 24 Jul 2026 20:50:10 +0000 [thread overview]
Message-ID: <178492621014.3303195.2965122653260784419.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260722151909.69142-1-leon.hwang@linux.dev>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Kumar Kartikeya Dwivedi <memxor@gmail.com>:
On Wed, 22 Jul 2026 23:19:07 +0800 you wrote:
> The trampoline could be corrupted by the blindly
> 'tr->flags = BPF_TRAMP_F_TAIL_CALL_CTX' in verifier.
>
> 1. A fexit attached to a tail_call_reachable prog. 'tr->flags' became
> 'BPF_TRAMP_F_CALL_ORIG | BPF_TRAMP_F_TAIL_CALL_CTX'. And, the
> trampoline would poke the target prog's nop insn using jmp insn instead
> of call insn.
> 2. Another fexit loaded with the same tail_call_reachable prog target.
> 'tr->flags' became 'BPF_TRAMP_F_TAIL_CALL_CTX'.
> 3. Close the first fexit link. Due to no BPF_TRAMP_F_CALL_ORIG in
> 'tr->flags', the trampoline will fail to restore the prog's nop insn
> using call insn.
>
> [...]
Here is the summary with links:
- [bpf-next,v2,1/2] bpf: Fix WARNING in bpf_tracing_link_release
https://git.kernel.org/bpf/bpf-next/c/61aaa8782bec
- [bpf-next,v2,2/2] selftests/bpf: Verify no warning when close fexit link
https://git.kernel.org/bpf/bpf-next/c/09e074666b7d
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-07-24 20:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-22 15:19 [PATCH bpf-next v2 0/2] bpf: Fix WARNING in bpf_tracing_link_release Leon Hwang
2026-07-22 15:19 ` [PATCH bpf-next v2 1/2] " Leon Hwang
2026-07-23 3:49 ` Pu Lehui
2026-07-22 15:19 ` [PATCH bpf-next v2 2/2] selftests/bpf: Verify no warning when close fexit link Leon Hwang
2026-07-23 4:08 ` Pu Lehui
2026-07-24 20:50 ` 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=178492621014.3303195.2965122653260784419.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=emil@etsalapatis.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kernel-patches-bot@fb.com \
--cc=leon.hwang@linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=maciej.fijalkowski@intel.com \
--cc=malin89@huawei.com \
--cc=martin.lau@linux.dev \
--cc=memxor@gmail.com \
--cc=pulehui@huawei.com \
--cc=shuah@kernel.org \
--cc=song@kernel.org \
--cc=tanjingguo@huawei.com \
--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