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, 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_trampoline_multi_detach
Date: Sun, 12 Jul 2026 00:00:13 +0000 [thread overview]
Message-ID: <178381441365.1241617.6815515077282154741.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260711124822.29406-1-leon.hwang@linux.dev>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Kumar Kartikeya Dwivedi <memxor@gmail.com>:
On Sat, 11 Jul 2026 20:48:20 +0800 you 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
>
> [...]
Here is the summary with links:
- [bpf-next,v2,1/2] bpf: Mark tracing_multi trampolines as ftrace managed
https://git.kernel.org/bpf/bpf-next/c/30bdd6d1384d
- [bpf-next,v2,2/2] selftests/bpf: Test fentry link after tracing_multi link
https://git.kernel.org/bpf/bpf-next/c/539d3edf8e53
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-12 0:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-11 12:48 [PATCH bpf-next v2 0/2] bpf: Fix WARNING in bpf_trampoline_multi_detach Leon Hwang
2026-07-11 12:48 ` [PATCH bpf-next v2 1/2] bpf: Mark tracing_multi trampolines as ftrace managed Leon Hwang
2026-07-11 12:48 ` [PATCH bpf-next v2 2/2] selftests/bpf: Test fentry link after tracing_multi link Leon Hwang
2026-07-11 20:36 ` Jiri Olsa
2026-07-12 0: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=178381441365.1241617.6815515077282154741.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=martin.lau@linux.dev \
--cc=memxor@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox