From: Tao Chen <chen.dylane@linux.dev>
To: Alexei Starovoitov <alexei.starovoitov@gmail.com>
Cc: Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii@kernel.org>,
Martin KaFai Lau <martin.lau@linux.dev>,
Eduard <eddyz87@gmail.com>, Song Liu <song@kernel.org>,
Yonghong Song <yonghong.song@linux.dev>,
John Fastabend <john.fastabend@gmail.com>,
KP Singh <kpsingh@kernel.org>,
Stanislav Fomichev <sdf@fomichev.me>, Hao Luo <haoluo@google.com>,
Jiri Olsa <jolsa@kernel.org>,
Matt Bobrowski <mattbobrowski@google.com>,
Steven Rostedt <rostedt@goodmis.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
bpf <bpf@vger.kernel.org>, LKML <linux-kernel@vger.kernel.org>,
linux-trace-kernel <linux-trace-kernel@vger.kernel.org>
Subject: Re: [PATCH bpf-next v3 2/2] bpf: Add show_fdinfo for kprobe_multi
Date: Thu, 19 Jun 2025 11:08:15 +0800 [thread overview]
Message-ID: <7b6ae7dc-1044-4551-bc3f-32430e34ba05@linux.dev> (raw)
In-Reply-To: <CAADnVQ+hT6nCGoR5a0Z+52SrJzO9-ReBRds23mBfrG3SbwGFdw@mail.gmail.com>
在 2025/6/19 09:46, Alexei Starovoitov 写道:
> On Mon, Jun 16, 2025 at 6:03 AM Tao Chen <chen.dylane@linux.dev> wrote:
>>
>> Show kprobe_multi link info with fdinfo, the info as follows:
>>
>> link_type: kprobe_multi
>> link_id: 1
>> prog_tag: a15b7646cb7f3322
>> prog_id: 21
>> type: kprobe_multi
>> kprobe_cnt: 8
>> missed: 0
>> cookie func
>> 1 bpf_fentry_test1
>> 7 bpf_fentry_test2
>> 2 bpf_fentry_test3
>> 3 bpf_fentry_test4
>> 4 bpf_fentry_test5
>> 5 bpf_fentry_test6
>> 6 bpf_fentry_test7
>> 8 bpf_fentry_test8
>>
>> Signed-off-by: Tao Chen <chen.dylane@linux.dev>
>> ---
>> kernel/trace/bpf_trace.c | 32 ++++++++++++++++++++++++++++++++
>> 1 file changed, 32 insertions(+)
>>
>> diff --git a/kernel/trace/bpf_trace.c b/kernel/trace/bpf_trace.c
>> index 2d422f897ac..fcf19e233b5 100644
>> --- a/kernel/trace/bpf_trace.c
>> +++ b/kernel/trace/bpf_trace.c
>> @@ -2623,10 +2623,42 @@ static int bpf_kprobe_multi_link_fill_link_info(const struct bpf_link *link,
>> return err;
>> }
>>
>> +#ifdef CONFIG_PROC_FS
>> +static void bpf_kprobe_multi_show_fdinfo(const struct bpf_link *link,
>> + struct seq_file *seq)
>> +{
>> + struct bpf_kprobe_multi_link *kmulti_link;
>> + char sym[KSYM_NAME_LEN];
>> +
>> + kmulti_link = container_of(link, struct bpf_kprobe_multi_link, link);
>> +
>> + seq_printf(seq,
>> + "type:\t%s\n"
>> + "kprobe_cnt:\t%u\n"
>> + "missed:\t%lu\n",
>> + kmulti_link->flags == BPF_F_KPROBE_MULTI_RETURN ? "kretprobe_multi" :
>> + "kprobe_multi",
>> + kmulti_link->cnt,
>> + kmulti_link->fp.nmissed);
>> +
>> + seq_printf(seq, "%-16s %-16s\n", "cookie", "func");
>> + for (int i = 0; i < kmulti_link->cnt; i++) {
>> + sprint_symbol_no_offset(sym, kmulti_link->addrs[i]);
>> + seq_printf(seq,
>> + "%-16llu %-16s\n",
>> + kmulti_link->cookies[i],
>> + sym);
>
> Why call sprint_symbol_no_offset() directly ?
> %pB is fine.
> +off doesn't disclose anything.
>
> pw-bot: cr
My problem, sorry for that, i had some issues with using printk to show
func name directly before. Actually, i used it incorrectly. How about
%pS, it looks more accurate. Thanks!
%pB format
cookie func
8 __pfx_bpf_fentry_test1+0x10/0x10
2 __pfx_bpf_fentry_test2+0x10/0x10
7 __pfx_bpf_fentry_test3+0x10/0x10
%pS format
cookie func
8 bpf_fentry_test1+0x0/0x20
2 bpf_fentry_test2+0x0/0x20
7 bpf_fentry_test3+0x0/0x20
--
Best Regards
Tao Chen
prev parent reply other threads:[~2025-06-19 3:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-16 13:02 [PATCH bpf-next v3 1/2] bpf: Add show_fdinfo for uprobe_multi Tao Chen
2025-06-16 13:02 ` [PATCH bpf-next v3 2/2] bpf: Add show_fdinfo for kprobe_multi Tao Chen
2025-06-19 1:46 ` Alexei Starovoitov
2025-06-19 3:08 ` Tao Chen [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=7b6ae7dc-1044-4551-bc3f-32430e34ba05@linux.dev \
--to=chen.dylane@linux.dev \
--cc=alexei.starovoitov@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).