bpf.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrii Nakryiko <andrii.nakryiko@gmail.com>
To: Yafang Shao <laoar.shao@gmail.com>
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
	 martin.lau@linux.dev, song@kernel.org, yhs@fb.com,
	john.fastabend@gmail.com,  kpsingh@kernel.org, sdf@google.com,
	haoluo@google.com, jolsa@kernel.org,  quentin@isovalent.com,
	bpf@vger.kernel.org
Subject: Re: [PATCH v2 bpf-next 03/11] bpftool: Show probed function in kprobe_multi link info
Date: Thu, 8 Jun 2023 16:08:07 -0700	[thread overview]
Message-ID: <CAEf4BzZsY=wT4BQTyMK5_MQamXo-vY1bLFc9rYGoxtnC1Maj=Q@mail.gmail.com> (raw)
In-Reply-To: <20230608103523.102267-4-laoar.shao@gmail.com>

On Thu, Jun 8, 2023 at 3:35 AM Yafang Shao <laoar.shao@gmail.com> wrote:
>
> Show the already expose kprobe_multi link info in bpftool. The result as
> follows,
>
> $ tools/bpf/bpftool/bpftool link show
> 4: kprobe_multi  prog 29
>         retprobe 0  func_cnt 4
>         addrs ffffffffb5d475b0  funcs schedule_timeout_interruptible
>               ffffffffb5d475f0        schedule_timeout_killable
>               ffffffffb5d47630        schedule_timeout_uninterruptible
>               ffffffffb5d47670        schedule_timeout_idle

what about module names? kallsyms has this information and it is quite
important, in addition to function name


>         pids trace(276245)
>
> $ tools/bpf/bpftool/bpftool link show -j
> [{"id":4,"type":"kprobe_multi","prog_id":29,"retprobe":0,"func_cnt":4,"funcs":[{"addr":18446744072465184176,"func":"schedule_timeout_interruptible"},{"addr":18446744072465184240,"func":"schedule_timeout_killable"},{"addr":18446744072465184304,"func":"schedule_timeout_uninterruptible"},{"addr":18446744072465184368,"func":"schedule_timeout_idle"}],"pids":[{"pid":276245,"comm":"trace"}]}]
>
> Signed-off-by: Yafang Shao <laoar.shao@gmail.com>
> ---
>  tools/bpf/bpftool/link.c | 82 ++++++++++++++++++++++++++++++++++++++++++++++++
>  1 file changed, 82 insertions(+)
>
> diff --git a/tools/bpf/bpftool/link.c b/tools/bpf/bpftool/link.c
> index 2d78607..c8033c3 100644
> --- a/tools/bpf/bpftool/link.c
> +++ b/tools/bpf/bpftool/link.c
> @@ -14,6 +14,7 @@
>
>  #include "json_writer.h"
>  #include "main.h"
> +#include "xlated_dumper.h"
>
>  static struct hashmap *link_table;
>
> @@ -166,6 +167,34 @@ static int get_prog_info(int prog_id, struct bpf_prog_info *info)
>         return err;
>  }
>
> +static void
> +show_kprobe_multi_json(struct bpf_link_info *info, json_writer_t *wtr)
> +{
> +       struct dump_data dd = {};
> +       const __u64 *addrs;
> +       __u32 i;
> +       int err;
> +
> +       jsonw_uint_field(json_wtr, "retprobe", info->kprobe_multi.retprobe);
> +       jsonw_uint_field(json_wtr, "func_cnt", info->kprobe_multi.count);
> +       jsonw_name(json_wtr, "funcs");
> +       jsonw_start_array(json_wtr);
> +       addrs = (const __u64 *)u64_to_ptr(info->kprobe_multi.addrs);
> +       err = kernel_syms_load(&dd, addrs, info->kprobe_multi.count);
> +       if (err) {
> +               jsonw_end_array(json_wtr);
> +               return;
> +       }
> +       for (i = 0; i < dd.sym_count; i++) {
> +               jsonw_start_object(json_wtr);
> +               jsonw_uint_field(json_wtr, "addr", dd.sym_mapping[i].address);
> +               jsonw_string_field(json_wtr, "func", dd.sym_mapping[i].name);
> +               jsonw_end_object(json_wtr);
> +       }
> +       jsonw_end_array(json_wtr);
> +       kernel_syms_destroy(&dd);
> +}
> +
>  static int show_link_close_json(int fd, struct bpf_link_info *info)
>  {
>         struct bpf_prog_info prog_info;
> @@ -218,6 +247,9 @@ static int show_link_close_json(int fd, struct bpf_link_info *info)
>                 jsonw_uint_field(json_wtr, "map_id",
>                                  info->struct_ops.map_id);
>                 break;
> +       case BPF_LINK_TYPE_KPROBE_MULTI:
> +               show_kprobe_multi_json(info, json_wtr);
> +               break;
>         default:
>                 break;
>         }
> @@ -351,6 +383,35 @@ void netfilter_dump_plain(const struct bpf_link_info *info)
>                 printf(" flags 0x%x", info->netfilter.flags);
>  }
>
> +static void show_kprobe_multi_plain(struct bpf_link_info *info)
> +{
> +       struct dump_data dd = {};
> +       const __u64 *addrs;
> +       __u32 i;
> +       int err;
> +
> +       if (!info->kprobe_multi.count)
> +               return;
> +
> +       printf("\n\tretprobe %d  func_cnt %u  ",
> +              info->kprobe_multi.retprobe, info->kprobe_multi.count);
> +       addrs = (const __u64 *)u64_to_ptr(info->kprobe_multi.addrs);
> +       err = kernel_syms_load(&dd, addrs, info->kprobe_multi.count);
> +       if (err)
> +               return;
> +       for (i = 0; i < dd.sym_count; i++) {
> +               if (!i)
> +                       printf("\n\taddrs %016lx  funcs %s  ",
> +                              dd.sym_mapping[i].address,
> +                              dd.sym_mapping[i].name);
> +               else
> +                       printf("\n\t      %016lx        %s  ",
> +                              dd.sym_mapping[i].address,
> +                              dd.sym_mapping[i].name);
> +       }
> +       kernel_syms_destroy(&dd);
> +}
> +
>  static int show_link_close_plain(int fd, struct bpf_link_info *info)
>  {
>         struct bpf_prog_info prog_info;
> @@ -396,6 +457,9 @@ static int show_link_close_plain(int fd, struct bpf_link_info *info)
>         case BPF_LINK_TYPE_NETFILTER:
>                 netfilter_dump_plain(info);
>                 break;
> +       case BPF_LINK_TYPE_KPROBE_MULTI:
> +               show_kprobe_multi_plain(info);
> +               break;
>         default:
>                 break;
>         }
> @@ -417,7 +481,9 @@ static int do_show_link(int fd)
>  {
>         struct bpf_link_info info;
>         __u32 len = sizeof(info);
> +       __u64 *addrs = NULL;
>         char buf[256];
> +       int count;
>         int err;
>
>         memset(&info, 0, sizeof(info));
> @@ -441,12 +507,28 @@ static int do_show_link(int fd)
>                 info.iter.target_name_len = sizeof(buf);
>                 goto again;
>         }
> +       if (info.type == BPF_LINK_TYPE_KPROBE_MULTI &&
> +           !info.kprobe_multi.addrs) {
> +               count = info.kprobe_multi.count;
> +               if (count) {
> +                       addrs = calloc(count, sizeof(__u64));
> +                       if (!addrs) {
> +                               p_err("mem alloc failed");
> +                               close(fd);
> +                               return -1;
> +                       }
> +                       info.kprobe_multi.addrs = (unsigned long)addrs;
> +                       goto again;
> +               }
> +       }
>
>         if (json_output)
>                 show_link_close_json(fd, &info);
>         else
>                 show_link_close_plain(fd, &info);
>
> +       if (addrs)
> +               free(addrs);
>         close(fd);
>         return 0;
>  }
> --
> 1.8.3.1
>

  reply	other threads:[~2023-06-08 23:08 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-08 10:35 [PATCH v2 bpf-next 00/11] bpf: Support ->fill_link_info for kprobe_multi and perf_event links Yafang Shao
2023-06-08 10:35 ` [PATCH v2 bpf-next 01/11] bpf: Support ->fill_link_info for kprobe_multi Yafang Shao
2023-06-08 23:05   ` Andrii Nakryiko
2023-06-09  9:13     ` Yafang Shao
2023-06-09 18:25       ` Andrii Nakryiko
2023-06-10  2:19         ` Yafang Shao
2023-06-08 10:35 ` [PATCH v2 bpf-next 02/11] bpftool: Add address filtering in kernel_syms_load() Yafang Shao
2023-06-08 10:35 ` [PATCH v2 bpf-next 03/11] bpftool: Show probed function in kprobe_multi link info Yafang Shao
2023-06-08 23:08   ` Andrii Nakryiko [this message]
2023-06-09  9:15     ` Yafang Shao
2023-06-08 10:35 ` [PATCH v2 bpf-next 04/11] bpf: Protect probed address based on kptr_restrict setting Yafang Shao
2023-06-08 23:08   ` Andrii Nakryiko
2023-06-09  9:16     ` Yafang Shao
2023-06-08 10:35 ` [PATCH v2 bpf-next 05/11] bpf: Clear the probe_addr for uprobe Yafang Shao
2023-06-08 10:35 ` [PATCH v2 bpf-next 06/11] bpf: Expose symbol addresses for precise identification Yafang Shao
2023-06-08 10:35 ` [PATCH v2 bpf-next 07/11] bpf: Add a common helper bpf_copy_to_user() Yafang Shao
2023-06-08 10:35 ` [PATCH v2 bpf-next 08/11] bpf: Support ->fill_link_info for perf_event Yafang Shao
2023-06-08 23:12   ` Andrii Nakryiko
2023-06-09  9:53     ` Yafang Shao
2023-06-09  9:56       ` Yafang Shao
2023-06-09 18:26         ` Andrii Nakryiko
2023-06-10  2:21           ` Yafang Shao
2023-06-08 10:35 ` [PATCH v2 bpf-next 09/11] libbpf: Add perf event names Yafang Shao
2023-06-08 23:14   ` Andrii Nakryiko
2023-06-09  4:36     ` Song Liu
2023-06-10  2:22       ` Yafang Shao
2023-06-10 20:34         ` Quentin Monnet
2023-06-11 15:52           ` Yafang Shao
2023-06-10 22:37       ` Jiri Olsa
2023-06-10 22:43   ` Jiri Olsa
2023-06-11 15:55     ` Yafang Shao
2023-06-08 10:35 ` [PATCH v2 bpf-next 10/11] bpftool: Move get_prog_info() into do_show_link() Yafang Shao
2023-06-08 10:35 ` [PATCH v2 bpf-next 11/11] bpftool: Show probed function in perf_event link info Yafang Shao

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='CAEf4BzZsY=wT4BQTyMK5_MQamXo-vY1bLFc9rYGoxtnC1Maj=Q@mail.gmail.com' \
    --to=andrii.nakryiko@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=jolsa@kernel.org \
    --cc=kpsingh@kernel.org \
    --cc=laoar.shao@gmail.com \
    --cc=martin.lau@linux.dev \
    --cc=quentin@isovalent.com \
    --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 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).