From: Tao Chen <chen.dylane@linux.dev>
To: Andrii Nakryiko <andrii.nakryiko@gmail.com>
Cc: kpsingh@kernel.org, mattbobrowski@google.com, song@kernel.org,
jolsa@kernel.org, ast@kernel.org, daniel@iogearbox.net,
andrii@kernel.org, martin.lau@linux.dev, eddyz87@gmail.com,
yonghong.song@linux.dev, john.fastabend@gmail.com,
sdf@fomichev.me, haoluo@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 v5 2/3] bpf: Add show_fdinfo for uprobe_multi
Date: Tue, 24 Jun 2025 16:42:06 +0800 [thread overview]
Message-ID: <3cdf1037-7e2d-4cc8-8298-10feee43deac@linux.dev> (raw)
In-Reply-To: <CAEf4BzY2dZ5KgcCH59rrQwZYaDZPt_-p4GHK8zMFP+RNPnNa=w@mail.gmail.com>
在 2025/6/24 06:14, Andrii Nakryiko 写道:
> On Mon, Jun 23, 2025 at 6:45 AM Tao Chen <chen.dylane@linux.dev> wrote:
>>
>> Show uprobe_multi link info with fdinfo, the info as follows:
>>
>> link_type: uprobe_multi
>> link_id: 10
>> prog_tag: 7db356c03e61a4d4
>> prog_id: 42
>> uprobe_cnt: 3
>> pid: 0
>> path: /home/dylane/bpf/tools/testing/selftests/bpf/test_progs
>> offset ref_ctr_offset cookie
>> 0xa69f13 0x0 2
>> 0xa69f1e 0x0 3
>> 0xa69f29 0x0 1
>>
>> Signed-off-by: Tao Chen <chen.dylane@linux.dev>
>> ---
>> kernel/trace/bpf_trace.c | 44 ++++++++++++++++++++++++++++++++++++++++
>> 1 file changed, 44 insertions(+)
>>
>> diff --git a/kernel/trace/bpf_trace.c b/kernel/trace/bpf_trace.c
>> index 8ecb1a9f85d..90209dda819 100644
>> --- a/kernel/trace/bpf_trace.c
>> +++ b/kernel/trace/bpf_trace.c
>> @@ -3171,10 +3171,54 @@ static int bpf_uprobe_multi_link_fill_link_info(const struct bpf_link *link,
>> return err;
>> }
>>
>> +#ifdef CONFIG_PROC_FS
>> +static void bpf_uprobe_multi_show_fdinfo(const struct bpf_link *link,
>> + struct seq_file *seq)
>> +{
>> + struct bpf_uprobe_multi_link *umulti_link;
>> + char *p, *buf;
>> +
>> + umulti_link = container_of(link, struct bpf_uprobe_multi_link, link);
>> +
>> + buf = kmalloc(PATH_MAX, GFP_KERNEL);
>> + if (!buf)
>> + return;
>> +
>> + p = d_path(&umulti_link->path, buf, PATH_MAX);
>> + if (IS_ERR(p)) {
>> + kfree(buf);
>> + return;
>> + }
>> +
>> + seq_printf(seq,
>> + "uprobe_cnt:\t%u\n"
>> + "pid:\t%u\n"
>> + "path:\t%s\n",
>> + umulti_link->cnt,
>> + umulti_link->task ? task_pid_nr_ns(umulti_link->task,
>> + task_active_pid_ns(current)) : 0,
>
> nit: either keep stuff like this on single line, or if it's too long
> or awkward, add a local variable. Formatting it like this is very hard
> to follow and looks pretty ugly...
>
will fix it in v6, thanks.
>> + p);
>> +
>> + seq_printf(seq, "%-16s %-16s %-16s\n", "offset", "ref_ctr_offset", "cookie");
>> + for (int i = 0; i < umulti_link->cnt; i++) {
>> + seq_printf(seq,
>> + "%#-16llx %#-16lx %-16llu\n",
>> + umulti_link->uprobes[i].offset,
>> + umulti_link->uprobes[i].ref_ctr_offset,
>> + umulti_link->uprobes[i].cookie);
>> + }
>> +
>> + kfree(buf);
>> +}
>> +#endif
>> +
>> static const struct bpf_link_ops bpf_uprobe_multi_link_lops = {
>> .release = bpf_uprobe_multi_link_release,
>> .dealloc_deferred = bpf_uprobe_multi_link_dealloc,
>> .fill_link_info = bpf_uprobe_multi_link_fill_link_info,
>> +#ifdef CONFIG_PROC_FS
>> + .show_fdinfo = bpf_uprobe_multi_show_fdinfo,
>> +#endif
>> };
>>
>> static int uprobe_prog_run(struct bpf_uprobe *uprobe,
>> --
>> 2.48.1
>>
--
Best Regards
Tao Chen
next prev parent reply other threads:[~2025-06-24 8:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250623134342.227347-1-chen.dylane@linux.dev>
2025-06-23 13:43 ` Tao Chen
2025-06-23 22:14 ` Andrii Nakryiko
2025-06-24 8:42 ` Tao Chen [this message]
2025-06-23 13:43 ` [PATCH bpf-next v5 3/3] bpf: Add show_fdinfo for kprobe_multi Tao Chen
2025-06-23 17:55 ` [PATCH bpf-next v5 1/3] bpf: Show precise link_type for {uprobe,kprobe}_multi fdinfo Alexei Starovoitov
2025-06-23 20:59 ` Andrii Nakryiko
2025-06-24 8:16 ` Jiri Olsa
2025-06-24 8:41 ` Tao Chen
2025-06-24 15:46 ` Andrii Nakryiko
2025-06-24 16:12 ` Tao Chen
2025-06-24 19:41 ` Andrii Nakryiko
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=3cdf1037-7e2d-4cc8-8298-10feee43deac@linux.dev \
--to=chen.dylane@linux.dev \
--cc=andrii.nakryiko@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
all inboxes | Powered by JetHome®