From: patchwork-bot+netdevbpf@kernel.org
To: chenyuan <chenyuan_fl@163.com>
Cc: alexei.starovoitov@gmail.com, ast@kernel.org,
leon.hwang@linux.dev, bpf@vger.kernel.org, daniel@iogearbox.net,
andrii@kernel.org, eddyz87@gmail.com, memxor@gmail.com,
martin.lau@linux.dev, yonghong.song@linux.dev,
john.fastabend@gmail.com, song@kernel.org,
ihor.solodrai@linux.dev, chenyuan@kylinos.cn
Subject: Re: [PATCH bpf-next v2 0/2] bpf: Keep target extended until its last freplace link detaches
Date: Thu, 24 Sep 2026 09:00:05 +0000 [thread overview]
Message-ID: <179024040591.1417542.4109230911556395227.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260924023737.1140521-1-chenyuan_fl@163.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Kumar Kartikeya Dwivedi <memxor@gmail.com>:
On Thu, 24 Sep 2026 10:37:35 +0800 you wrote:
> From: Yuan Chen <chenyuan@kylinos.cn>
>
> is_extended is a plain boolean, but one target prog can carry several
> freplace links at the same time, one on its entry and one on a global
> subprogram. __bpf_trampoline_unlink_prog() cleared it whenever *any*
> of them detached, so with two links on one target, detaching one of
> them re-armed the unbounded tail call loop closed by commit
> d6083f040d5d ("bpf: Prevent tailcall infinite loop caused by freplace"):
> a single BPF_PROG_TEST_RUN on the tail-called target then panics the
> kernel, reproduced on both bpf-next and master.
>
> [...]
Here is the summary with links:
- [bpf-next,v2,1/2] bpf: Keep target extended until its last freplace link detaches
https://git.kernel.org/bpf/bpf-next/c/c43c348a8446
- [bpf-next,v2,2/2] selftests/bpf: Verify is_extended with multiple freplace links
https://git.kernel.org/bpf/bpf-next/c/01d37848bf5b
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-09-24 9:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-24 2:37 [PATCH bpf-next v2 0/2] bpf: Keep target extended until its last freplace link detaches chenyuan_fl
2026-09-24 2:37 ` [PATCH bpf-next v2 1/2] " chenyuan_fl
2026-09-24 7:06 ` Leon Hwang
2026-09-24 9:48 ` Jiri Olsa
2026-09-24 9:58 ` chenyuan
2026-09-25 4:35 ` [PATCH bpf-next] bpf: Roll back freplace link state when bpf_arch_text_poke() fails chenyuan_fl
2026-09-25 5:18 ` bot+bpf-ci
2026-09-25 6:05 ` Leon Hwang
2026-09-28 9:08 ` chenyuan
2026-09-24 2:37 ` [PATCH bpf-next v2 2/2] selftests/bpf: Verify is_extended with multiple freplace links chenyuan_fl
2026-09-24 7:06 ` Leon Hwang
2026-09-24 8:42 ` [PATCH bpf-next v2 0/2] bpf: Keep target extended until its last freplace link detaches Jiri Olsa
2026-09-24 9:00 ` 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=179024040591.1417542.4109230911556395227.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alexei.starovoitov@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=chenyuan@kylinos.cn \
--cc=chenyuan_fl@163.com \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=ihor.solodrai@linux.dev \
--cc=john.fastabend@gmail.com \
--cc=leon.hwang@linux.dev \
--cc=martin.lau@linux.dev \
--cc=memxor@gmail.com \
--cc=song@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