From: Leon Hwang <leon.hwang@linux.dev>
To: chenyuan_fl@163.com, bpf@vger.kernel.org
Cc: linux-kernel@vger.kernel.org,
Alexei Starovoitov <alexei.starovoitov@gmail.com>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii@kernel.org>,
Eduard Zingerman <eddyz87@gmail.com>,
Kumar Kartikeya Dwivedi <memxor@gmail.com>,
Martin KaFai Lau <martin.lau@linux.dev>,
Song Liu <song@kernel.org>,
Yonghong Song <yonghong.song@linux.dev>,
Jiri Olsa <jolsa@kernel.org>,
Ihor Solodrai <ihor.solodrai@linux.dev>,
Yuan Chen <chenyuan@kylinos.cn>
Subject: Re: [PATCH bpf-next 1/2] bpf: Keep target extended until its last freplace link detaches
Date: Wed, 23 Sep 2026 17:54:33 +0800 [thread overview]
Message-ID: <ee0a1126-9ff2-4a08-8f13-4af366ebe28a@linux.dev> (raw)
In-Reply-To: <20260923090635.368488-2-chenyuan_fl@163.com>
On 23/9/26 17:06, chenyuan_fl@163.com wrote:
> From: Yuan Chen <chenyuan@kylinos.cn>
>
> The is_extended / prog_array_member_cnt protocol introduced by commit
> d6083f040d5d ("bpf: Prevent tailcall infinite loop caused by freplace")
> keeps a prog extended by a freplace program out of prog_array maps, and
> vice versa: once a tail call re-enters an extended subprogram, its
> tail_call_cnt resets on every execution and the loop never terminates.
>
> But is_extended is a plain boolean, while 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 is_extended
> whenever *any* freplace link detached, so detaching one of two links
> re-armed the unbounded loop through the remaining one.
>
> Replace the is_extended boolean with a count of the freplace links
> attached to each target prog, so the target stays extended until its
> last link detaches. Also rename bpf_freplace_check_tgt_prog() to
> bpf_freplace_link_tgt_prog(), as the helper has never been a pure
> check: it reserves the target prog on success.
>
> Fixes: d6083f040d5d ("bpf: Prevent tailcall infinite loop caused by freplace")
You should cc me when posting the next revision.
You can get the cc list by ./scripts/get_maintainer.pl /path/to/file.patch.
> Signed-off-by: Yuan Chen <chenyuan@kylinos.cn>
> ---
> include/linux/bpf.h | 4 ++--
> kernel/bpf/arraymap.c | 2 +-
> kernel/bpf/trampoline.c | 10 ++++++----
> 3 files changed, 9 insertions(+), 7 deletions(-)
>
[...]
>
> @@ -933,7 +933,7 @@ static int __bpf_trampoline_link_prog(struct bpf_tramp_node *node,
> /* Cannot attach extension if fentry/fexit are in use. */
> if (cnt)
> return -EBUSY;
> - err = bpf_freplace_check_tgt_prog(tgt_prog);
> + err = bpf_freplace_link_tgt_prog(tgt_prog);
> if (err)
> return err;
> tr->extension_prog = node->link->prog;
> @@ -979,7 +979,9 @@ static int __bpf_trampoline_unlink_prog(struct bpf_tramp_node *node,
> tr->extension_prog->bpf_func, NULL);
> tr->extension_prog = NULL;
> guard(mutex)(&tgt_prog->aux->ext_mutex);
> - tgt_prog->aux->is_extended = false;
> + if (WARN_ON_ONCE(!tgt_prog->aux->freplace_link_cnt))
Is this WARN_ON_ONCE() necessary?
Thanks,
Leon
> + return err;
> + tgt_prog->aux->freplace_link_cnt--;
> return err;
> }
> bpf_trampoline_remove_prog(tr, node);
next prev parent reply other threads:[~2026-09-23 9:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-23 9:06 [PATCH bpf-next 0/2] " chenyuan_fl
2026-09-23 9:06 ` [PATCH bpf-next 1/2] " chenyuan_fl
2026-09-23 9:54 ` Leon Hwang [this message]
2026-09-23 10:02 ` bot+bpf-ci
2026-09-23 22:14 ` Alexei Starovoitov
2026-09-23 9:06 ` [PATCH bpf-next 2/2] selftests/bpf: Verify is_extended with multiple freplace links chenyuan_fl
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=ee0a1126-9ff2-4a08-8f13-4af366ebe28a@linux.dev \
--to=leon.hwang@linux.dev \
--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=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®