From: Jiri Olsa <olsajiri@gmail.com>
To: Yafang Shao <laoar.shao@gmail.com>
Cc: ast@kernel.org, daniel@iogearbox.net, john.fastabend@gmail.com,
andrii@kernel.org, martin.lau@linux.dev, song@kernel.org,
yhs@fb.com, kpsingh@kernel.org, sdf@google.com,
haoluo@google.com, quentin@isovalent.com, rostedt@goodmis.org,
mhiramat@kernel.org, bpf@vger.kernel.org,
linux-trace-kernel@vger.kernel.org
Subject: Re: [PATCH v6 bpf-next 00/11] bpf: Support ->fill_link_info for kprobe_multi and perf_event links
Date: Thu, 29 Jun 2023 15:29:14 +0200 [thread overview]
Message-ID: <ZJ2HKgg5jsLxiwX6@krava> (raw)
In-Reply-To: <20230628115329.248450-1-laoar.shao@gmail.com>
On Wed, Jun 28, 2023 at 11:53:18AM +0000, Yafang Shao wrote:
> This patchset enhances the usability of kprobe_multi program by introducing
> support for ->fill_link_info. This allows users to easily determine the
> probed functions associated with a kprobe_multi program. While
> `bpftool perf show` already provides information about functions probed by
> perf_event programs, supporting ->fill_link_info ensures consistent access
> to this information across all bpf links.
>
> In addition, this patch extends support to generic perf events, which are
> currently not covered by `bpftool perf show`. While userspace is exposed to
> only the perf type and config, other attributes such as sample_period and
> sample_freq are disregarded.
>
> To ensure accurate identification of probed functions, it is preferable to
> expose the address directly rather than relying solely on the symbol name.
> However, this implementation respects the kptr_restrict setting and avoids
> exposing the address if it is not permitted.
>
> v5->v6:
> - From Andrii
> - if ucount is too less, copy ucount items and return -E2BIG
> - zero out kmulti_link->cnt elements if it is not permitted by kptr
> - avoid leaking information when ucount is greater than kmulti_link->cnt
> - drop the flags, and add BPF_PERF_EVENT_[UK]RETPROBE
> - From Quentin
> - use jsonw_null instead when we have no module name
> - add explanation on perf_type_name in the commit log
> - avoid the unnecessary out lable
Acked-by: Jiri Olsa <jolsa@kernel.org>
jirka
prev parent reply other threads:[~2023-06-29 13:29 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-28 11:53 [PATCH v6 bpf-next 00/11] bpf: Support ->fill_link_info for kprobe_multi and perf_event links Yafang Shao
2023-06-28 11:53 ` [PATCH v6 bpf-next 01/11] bpf: Support ->fill_link_info for kprobe_multi Yafang Shao
2023-07-06 22:00 ` Andrii Nakryiko
2023-07-07 1:52 ` Yafang Shao
2023-06-28 11:53 ` [PATCH v6 bpf-next 02/11] bpftool: Dump the kernel symbol's module name Yafang Shao
2023-06-29 13:46 ` Quentin Monnet
2023-06-30 2:22 ` Yafang Shao
2023-06-28 11:53 ` [PATCH v6 bpf-next 03/11] bpftool: Show kprobe_multi link info Yafang Shao
2023-07-05 8:09 ` Daniel Borkmann
2023-07-05 9:59 ` Yafang Shao
2023-06-28 11:53 ` [PATCH v6 bpf-next 04/11] bpf: Protect probed address based on kptr_restrict setting Yafang Shao
2023-06-28 11:53 ` [PATCH v6 bpf-next 05/11] bpf: Clear the probe_addr for uprobe Yafang Shao
2023-07-05 8:19 ` Daniel Borkmann
2023-07-05 10:00 ` Yafang Shao
2023-07-05 14:33 ` Yafang Shao
2023-06-28 11:53 ` [PATCH v6 bpf-next 06/11] bpf: Expose symbol's respective address Yafang Shao
2023-07-05 8:26 ` Daniel Borkmann
2023-07-05 10:01 ` Yafang Shao
2023-06-28 11:53 ` [PATCH v6 bpf-next 07/11] bpf: Add a common helper bpf_copy_to_user() Yafang Shao
2023-07-06 22:00 ` Andrii Nakryiko
2023-06-28 11:53 ` [PATCH v6 bpf-next 08/11] bpf: Add bpf_perf_link_fill_common() Yafang Shao
2023-07-06 22:00 ` Andrii Nakryiko
2023-07-07 1:49 ` Yafang Shao
2023-06-28 11:53 ` [PATCH v6 bpf-next 09/11] bpf: Support ->fill_link_info for perf_event Yafang Shao
2023-07-05 8:46 ` Daniel Borkmann
2023-07-05 10:08 ` Yafang Shao
2023-07-05 12:30 ` Daniel Borkmann
2023-06-28 11:53 ` [PATCH v6 bpf-next 10/11] bpftool: Add perf event names Yafang Shao
2023-06-28 11:53 ` [PATCH v6 bpf-next 11/11] bpftool: Show perf link info Yafang Shao
2023-06-29 13:40 ` Quentin Monnet
2023-07-05 8:54 ` Daniel Borkmann
2023-07-05 10:13 ` Yafang Shao
2023-06-29 13:29 ` Jiri Olsa [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=ZJ2HKgg5jsLxiwX6@krava \
--to=olsajiri@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=kpsingh@kernel.org \
--cc=laoar.shao@gmail.com \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=mhiramat@kernel.org \
--cc=quentin@isovalent.com \
--cc=rostedt@goodmis.org \
--cc=sdf@google.com \
--cc=song@kernel.org \
--cc=yhs@fb.com \
/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.