From: Leon Hwang <leon.hwang@linux.dev>
To: Jiri Olsa <olsajiri@gmail.com>
Cc: bpf@vger.kernel.org, Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
John Fastabend <john.fastabend@gmail.com>,
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>,
Emil Tsalapatis <emil@etsalapatis.com>,
Shuah Khan <shuah@kernel.org>,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
kernel-patches-bot@fb.com
Subject: Re: [PATCH bpf-next 1/2] bpf: Mark tracing_multi trampolines as ftrace managed
Date: Sat, 11 Jul 2026 20:09:28 +0800 [thread overview]
Message-ID: <3b473dcf-54de-4925-8939-4a8c08f48341@linux.dev> (raw)
In-Reply-To: <alFvBaC7moSlJMh6@krava>
On 2026/7/11 06:15, Jiri Olsa wrote:
> On Fri, Jul 10, 2026 at 10:47:33PM +0800, Leon Hwang wrote:
>> Since tracing_multi link does not set ftrace_managed, it would fail to
>> release the tracing_multi link when attaching tracing_multi link and
>> then attaching fentry link.
>>
>> [ 3.714215] WARNING: kernel/bpf/trampoline.c:1727 at bpf_trampoline_multi_detach+0x20b/0x240, CPU#1: test_progs/97
>> ...
>> [ 3.733170] bpf_tracing_multi_link_release+0x14/0x30
>> [ 3.733890] bpf_link_free+0x58/0x130
>> [ 3.734414] bpf_link_release+0x23/0x30
>>
>> Fix it by setting 'ftrace_managed = true' in register_fentry_multi().
>>
>> Fixes: aef4dfa790b2 ("bpf: Add bpf_trampoline_multi_attach/detach functions")
>> Signed-off-by: Leon Hwang <leon.hwang@linux.dev>
>> ---
>> kernel/bpf/trampoline.c | 1 +
>> 1 file changed, 1 insertion(+)
>>
>> diff --git a/kernel/bpf/trampoline.c b/kernel/bpf/trampoline.c
>> index 1a721fc4bef5..6eadf64f7ec9 100644
>> --- a/kernel/bpf/trampoline.c
>> +++ b/kernel/bpf/trampoline.c
>> @@ -1536,6 +1536,7 @@ static int register_fentry_multi(struct bpf_trampoline *tr, struct bpf_tramp_ima
>> if (bpf_trampoline_use_jmp(tr->flags))
>> addr = ftrace_jmp_set(addr);
>>
>> + tr->func.ftrace_managed = true;
>
> I wonder we could set tr->func.ftrace_managed early in bpf_trampoline_get,
> but we could do that as follow up
Makes sense. Let me try it when adding tracing_multi link support for
bpf progs.
>
> Acked-by: Jiri Olsa <jolsa@kernel.org>
Thanks for your review.
Leon
>
> thanks,
> jirka
>
>
>> ftrace_hash_add(data->reg, data->entry, ip, addr);
>> tr->cur_image = im;
>> return 0;
>> --
>> 2.55.0
>>
next prev parent reply other threads:[~2026-07-11 12:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-10 14:47 [PATCH bpf-next 0/2] bpf: Fix WARNING in bpf_trampoline_multi_detach Leon Hwang
2026-07-10 14:47 ` [PATCH bpf-next 1/2] bpf: Mark tracing_multi trampolines as ftrace managed Leon Hwang
2026-07-10 22:15 ` Jiri Olsa
2026-07-11 12:09 ` Leon Hwang [this message]
2026-07-10 14:47 ` [PATCH bpf-next 2/2] selftests/bpf: Test fentry link after tracing_multi link Leon Hwang
2026-07-10 15:04 ` sashiko-bot
2026-07-10 15:14 ` Leon Hwang
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=3b473dcf-54de-4925-8939-4a8c08f48341@linux.dev \
--to=leon.hwang@linux.dev \
--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=kernel-patches-bot@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=memxor@gmail.com \
--cc=olsajiri@gmail.com \
--cc=shuah@kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.