linux-trace-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tao Chen <chen.dylane@linux.dev>
To: Jiri Olsa <olsajiri@gmail.com>
Cc: song@kernel.org, kpsingh@kernel.org, mattbobrowski@google.com,
	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 v2 1/2] bpf: Add show_fdinfo for uprobe_multi
Date: Mon, 16 Jun 2025 16:39:35 +0800	[thread overview]
Message-ID: <fdc58e38-8b54-4681-89e9-78f8941db1b0@linux.dev> (raw)
In-Reply-To: <aE_KX66K-8yrSPtS@krava>

在 2025/6/16 15:40, Jiri Olsa 写道:
> On Sun, Jun 15, 2025 at 11:05:13PM +0800, Tao Chen wrote:
>> Show uprobe_multi link info with fdinfo, the info as follows:
>>
>> link_type:	uprobe_multi
>> link_id:	9
>> prog_tag:	e729f789e34a8eca
>> prog_id:	58
>> type:	uprobe_multi
>> uprobe_cnt:	3
>> pid:	0
>> path:	/home/dylane/bpf/tools/testing/selftests/bpf/test_progs
>> offset:	0xa69ed7
>> ref_ctr_offset:	0x0
>> cookie:	3
>> offset:	0xa69ee2
>> ref_ctr_offset:	0x0
>> cookie:	1
>> offset:	0xa69eed
>> ref_ctr_offset:	0x0
>> cookie:	2
> 
> hi,
> does this need to be 'tag: value' format ? bpftool uses:
> 
>          offset             ref_ctr_offset     cookies
>          0xe558             0x0                0x0
>          0x2574e            0x0                0x0
>          0x6c393            0x0                0x0
> 
> which might be more readable, or at least extra line after each uprobe?
> also using spaces instead of tabs  to align the values might help
> 
> same for kprobe_multi, otherwise looks lgtm
> 

That's a great suggestion, it does look more concise. I will change it 
in v3, thanks!

> thanks,
> jirka
> 
> 
>>
>> Signed-off-by: Tao Chen <chen.dylane@linux.dev>
>> ---
>>   kernel/trace/bpf_trace.c | 48 ++++++++++++++++++++++++++++++++++++++++
>>   1 file changed, 48 insertions(+)
>>
>> Change list:
>>    v1 -> v2:
>>      - replace 'func_cnt' with 'uprobe_cnt'.(Andrii)
>>      - print func name is more readable and security for kprobe_multi.(Alexei)
>>    v1:
>>    https://lore.kernel.org/bpf/20250612115556.295103-1-chen.dylane@linux.dev
>>
>> diff --git a/kernel/trace/bpf_trace.c b/kernel/trace/bpf_trace.c
>> index 24b94870b50..9a8ca8a8e2b 100644
>> --- a/kernel/trace/bpf_trace.c
>> +++ b/kernel/trace/bpf_trace.c
>> @@ -3157,10 +3157,58 @@ 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,
>> +		   "type:\t%s\n"
>> +		   "uprobe_cnt:\t%u\n"
>> +		   "pid:\t%u\n"
>> +		   "path:\t%s\n",
>> +		   umulti_link->flags == BPF_F_UPROBE_MULTI_RETURN ?
>> +					 "uretprobe_multi" : "uprobe_multi",
>> +		   umulti_link->cnt,
>> +		   umulti_link->task ? task_pid_nr_ns(umulti_link->task,
>> +			   task_active_pid_ns(current)) : 0,
>> +		   p);
>> +
>> +	for (int i = 0; i < umulti_link->cnt; i++) {
>> +		seq_printf(seq,
>> +			   "offset:\t%#llx\n"
>> +			   "ref_ctr_offset:\t%#lx\n"
>> +			   "cookie:\t%llu\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

      reply	other threads:[~2025-06-16  8:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-15 15:05 [PATCH bpf-next v2 1/2] bpf: Add show_fdinfo for uprobe_multi Tao Chen
2025-06-15 15:05 ` [PATCH bpf-next v2 2/2] bpf: Add show_fdinfo for kprobe_multi Tao Chen
2025-06-16  7:40   ` Jiri Olsa
2025-06-16  8:34     ` Tao Chen
2025-06-16  7:40 ` [PATCH bpf-next v2 1/2] bpf: Add show_fdinfo for uprobe_multi Jiri Olsa
2025-06-16  8:39   ` 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=fdc58e38-8b54-4681-89e9-78f8941db1b0@linux.dev \
    --to=chen.dylane@linux.dev \
    --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=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=olsajiri@gmail.com \
    --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).