From: patchwork-bot+netdevbpf@kernel.org
To: Tao Chen <chen.dylane@linux.dev>
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
martin.lau@linux.dev, eddyz87@gmail.com, song@kernel.org,
yonghong.song@linux.dev, john.fastabend@gmail.com,
kpsingh@kernel.org, sdf@fomichev.me, haoluo@google.com,
jolsa@kernel.org, mattbobrowski@google.com, rostedt@goodmis.org,
mhiramat@kernel.org, mathieu.desnoyers@efficios.com,
bpf@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-trace-kernel@vger.kernel.org
Subject: Re: [PATCH bpf-next v7 1/3] bpf: Show precise link_type for {uprobe,kprobe}_multi fdinfo
Date: Fri, 04 Jul 2025 02:40:37 +0000 [thread overview]
Message-ID: <175159683750.1682876.3979686281569023976.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250702153958.639852-1-chen.dylane@linux.dev>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Wed, 2 Jul 2025 23:39:56 +0800 you wrote:
> Alexei suggested, 'link_type' can be more precise and differentiate
> for human in fdinfo. In fact BPF_LINK_TYPE_KPROBE_MULTI includes
> kretprobe_multi type, the same as BPF_LINK_TYPE_UPROBE_MULTI, so we
> can show it more concretely.
>
> link_type: kprobe_multi
> link_id: 1
> prog_tag: d2b307e915f0dd37
> ...
> link_type: kretprobe_multi
> link_id: 2
> prog_tag: ab9ea0545870781d
> ...
> link_type: uprobe_multi
> link_id: 9
> prog_tag: e729f789e34a8eca
> ...
> link_type: uretprobe_multi
> link_id: 10
> prog_tag: 7db356c03e61a4d4
>
> [...]
Here is the summary with links:
- [bpf-next,v7,1/3] bpf: Show precise link_type for {uprobe,kprobe}_multi fdinfo
https://git.kernel.org/bpf/bpf-next/c/803f0700a3bb
- [bpf-next,v7,2/3] bpf: Add show_fdinfo for uprobe_multi
https://git.kernel.org/bpf/bpf-next/c/b4dfe26fbf56
- [bpf-next,v7,3/3] bpf: Add show_fdinfo for kprobe_multi
https://git.kernel.org/bpf/bpf-next/c/da7e9c0a7fbc
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:[~2025-07-04 2:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-02 15:39 [PATCH bpf-next v7 1/3] bpf: Show precise link_type for {uprobe,kprobe}_multi fdinfo Tao Chen
2025-07-02 15:39 ` [PATCH bpf-next v7 2/3] bpf: Add show_fdinfo for uprobe_multi Tao Chen
2025-07-02 15:39 ` [PATCH bpf-next v7 3/3] bpf: Add show_fdinfo for kprobe_multi Tao Chen
2025-07-04 2:40 ` 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=175159683750.1682876.3979686281569023976.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=chen.dylane@linux.dev \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=mathieu.desnoyers@efficios.com \
--cc=mattbobrowski@google.com \
--cc=mhiramat@kernel.org \
--cc=rostedt@goodmis.org \
--cc=sdf@fomichev.me \
--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.