From: Jiri Olsa <olsajiri@gmail.com>
To: Andrii Nakryiko <andrii.nakryiko@gmail.com>
Cc: Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii@kernel.org>,
bpf@vger.kernel.org, Martin KaFai Lau <kafai@fb.com>,
Song Liu <songliubraving@fb.com>, Yonghong Song <yhs@fb.com>,
John Fastabend <john.fastabend@gmail.com>,
KP Singh <kpsingh@chromium.org>,
Stanislav Fomichev <sdf@google.com>, Hao Luo <haoluo@google.com>,
Viktor Malik <vmalik@redhat.com>,
"Masami Hiramatsu (Google)" <mhiramat@kernel.org>
Subject: Re: [PATCH bpf-next 6/7] selftests/bpf: Add kprobe multi session test
Date: Wed, 24 Apr 2024 13:44:50 +0200 [thread overview]
Message-ID: <ZijwsrKWCbo57vUE@krava> (raw)
In-Reply-To: <CAEf4Bza2oReiAMhO3bUwP9LmdQ=+u98gEd2Vz_zGmB1PUVi4-Q@mail.gmail.com>
On Tue, Apr 23, 2024 at 05:27:14PM -0700, Andrii Nakryiko wrote:
> On Mon, Apr 22, 2024 at 5:13 AM Jiri Olsa <jolsa@kernel.org> wrote:
SNIP
> > diff --git a/tools/testing/selftests/bpf/prog_tests/kprobe_multi_test.c b/tools/testing/selftests/bpf/prog_tests/kprobe_multi_test.c
> > index 51628455b6f5..d1f116665551 100644
> > --- a/tools/testing/selftests/bpf/prog_tests/kprobe_multi_test.c
> > +++ b/tools/testing/selftests/bpf/prog_tests/kprobe_multi_test.c
> > @@ -4,6 +4,7 @@
> > #include "trace_helpers.h"
> > #include "kprobe_multi_empty.skel.h"
> > #include "kprobe_multi_override.skel.h"
> > +#include "kprobe_multi_session.skel.h"
> > #include "bpf/libbpf_internal.h"
> > #include "bpf/hashmap.h"
> >
> > @@ -326,6 +327,52 @@ static void test_attach_api_fails(void)
> > kprobe_multi__destroy(skel);
> > }
> >
> > +static void test_session_skel_api(void)
> > +{
> > + struct kprobe_multi_session *skel = NULL;
> > + LIBBPF_OPTS(bpf_kprobe_multi_opts, opts);
> > + LIBBPF_OPTS(bpf_test_run_opts, topts);
> > + struct bpf_link *link = NULL;
> > + int err, prog_fd;
> > +
> > + skel = kprobe_multi_session__open_and_load();
> > + if (!ASSERT_OK_PTR(skel, "kprobe_multi_session__open_and_load"))
> > + goto cleanup;
>
> return?
ok
>
> > +
> > + skel->bss->pid = getpid();
> > +
> > + err = kprobe_multi_session__attach(skel);
>
> nit: extra space
>
> > + if (!ASSERT_OK(err, " kprobe_multi_session__attach"))
> > + goto cleanup;
> > +
> > + prog_fd = bpf_program__fd(skel->progs.trigger);
> > + err = bpf_prog_test_run_opts(prog_fd, &topts);
> > + ASSERT_OK(err, "test_run");
> > + ASSERT_EQ(topts.retval, 0, "test_run");
> > +
> > + ASSERT_EQ(skel->bss->kprobe_test1_result, 1, "kprobe_test1_result");
> > + ASSERT_EQ(skel->bss->kprobe_test2_result, 1, "kprobe_test2_result");
> > + ASSERT_EQ(skel->bss->kprobe_test3_result, 1, "kprobe_test3_result");
> > + ASSERT_EQ(skel->bss->kprobe_test4_result, 1, "kprobe_test4_result");
> > + ASSERT_EQ(skel->bss->kprobe_test5_result, 1, "kprobe_test5_result");
> > + ASSERT_EQ(skel->bss->kprobe_test6_result, 1, "kprobe_test6_result");
> > + ASSERT_EQ(skel->bss->kprobe_test7_result, 1, "kprobe_test7_result");
> > + ASSERT_EQ(skel->bss->kprobe_test8_result, 1, "kprobe_test8_result");
> > +
> > + ASSERT_EQ(skel->bss->kretprobe_test1_result, 0, "kretprobe_test1_result");
> > + ASSERT_EQ(skel->bss->kretprobe_test2_result, 1, "kretprobe_test2_result");
> > + ASSERT_EQ(skel->bss->kretprobe_test3_result, 0, "kretprobe_test3_result");
> > + ASSERT_EQ(skel->bss->kretprobe_test4_result, 1, "kretprobe_test4_result");
> > + ASSERT_EQ(skel->bss->kretprobe_test5_result, 0, "kretprobe_test5_result");
> > + ASSERT_EQ(skel->bss->kretprobe_test6_result, 1, "kretprobe_test6_result");
> > + ASSERT_EQ(skel->bss->kretprobe_test7_result, 0, "kretprobe_test7_result");
> > + ASSERT_EQ(skel->bss->kretprobe_test8_result, 1, "kretprobe_test8_result");
>
> see below, even if array of ksym ptrs idea doesn't work out, at least
> results can be an array (which is cleaner to work with both on BPF and
> user space sides)
I recall in past we used to do that and we switched to specific values
to be more explicit I guess.. but it might make sense in here, will try it
SNIP
> > +static int session_check(void *ctx, bool is_return)
> > +{
> > + if (bpf_get_current_pid_tgid() >> 32 != pid)
> > + return 1;
> > +
> > + __u64 addr = bpf_get_func_ip(ctx);
> > +
> > +#define SET(__var, __addr) ({ \
> > + if ((const void *) addr == __addr) \
> > + __var = 1; \
> > +})
> > +
> > + if (is_return) {
> > + SET(kretprobe_test1_result, &bpf_fentry_test1);
> > + SET(kretprobe_test2_result, &bpf_fentry_test2);
> > + SET(kretprobe_test3_result, &bpf_fentry_test3);
> > + SET(kretprobe_test4_result, &bpf_fentry_test4);
> > + SET(kretprobe_test5_result, &bpf_fentry_test5);
> > + SET(kretprobe_test6_result, &bpf_fentry_test6);
> > + SET(kretprobe_test7_result, &bpf_fentry_test7);
> > + SET(kretprobe_test8_result, &bpf_fentry_test8);
> > + } else {
> > + SET(kprobe_test1_result, &bpf_fentry_test1);
> > + SET(kprobe_test2_result, &bpf_fentry_test2);
> > + SET(kprobe_test3_result, &bpf_fentry_test3);
> > + SET(kprobe_test4_result, &bpf_fentry_test4);
> > + SET(kprobe_test5_result, &bpf_fentry_test5);
> > + SET(kprobe_test6_result, &bpf_fentry_test6);
> > + SET(kprobe_test7_result, &bpf_fentry_test7);
> > + SET(kprobe_test8_result, &bpf_fentry_test8);
> > + }
> > +
> > +#undef SET
>
> curious, have you tried implementing this through a proper for loop? I
> wonder if something like
>
> void *kfuncs[] = { &bpf_fentry_test1, ..., &bpf_fentry_test8 };
>
> and then generic loop over this array would work. Can you please try?
yep, will try, let's see if it gets nicer
jirka
next prev parent reply other threads:[~2024-04-24 11:44 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-22 12:12 [PATCH bpf-next 0/7] bpf: Introduce kprobe_multi session attach Jiri Olsa
2024-04-22 12:12 ` [PATCH bpf-next 1/7] bpf: Add support for kprobe multi " Jiri Olsa
2024-04-24 0:26 ` Andrii Nakryiko
2024-04-24 11:46 ` Jiri Olsa
2024-04-22 12:12 ` [PATCH bpf-next 2/7] bpf: Add support for kprobe multi session context Jiri Olsa
2024-04-24 0:26 ` Andrii Nakryiko
2024-04-24 11:45 ` Jiri Olsa
2024-04-22 12:12 ` [PATCH bpf-next 3/7] bpf: Add support for kprobe multi session cookie Jiri Olsa
2024-04-22 17:48 ` Alexei Starovoitov
2024-04-22 20:55 ` Jiri Olsa
2024-04-24 0:26 ` Andrii Nakryiko
2024-04-24 11:45 ` Jiri Olsa
2024-04-22 12:12 ` [PATCH bpf-next 4/7] libbpf: Add support for kprobe multi session attach Jiri Olsa
2024-04-24 0:26 ` Andrii Nakryiko
2024-04-24 11:45 ` Jiri Olsa
2024-04-22 12:12 ` [PATCH bpf-next 5/7] libbpf: Add kprobe session attach type name to attach_type_name Jiri Olsa
2024-04-24 0:27 ` Andrii Nakryiko
2024-04-24 11:44 ` Jiri Olsa
2024-04-22 12:12 ` [PATCH bpf-next 6/7] selftests/bpf: Add kprobe multi session test Jiri Olsa
2024-04-24 0:27 ` Andrii Nakryiko
2024-04-24 11:44 ` Jiri Olsa [this message]
2024-04-30 8:10 ` Jiri Olsa
2024-04-22 12:12 ` [PATCH bpf-next 7/7] selftests/bpf: Add kprobe multi wrapper cookie test Jiri Olsa
2024-04-24 0:27 ` Andrii Nakryiko
2024-04-24 11:44 ` Jiri Olsa
2024-04-24 0:27 ` [PATCH bpf-next 0/7] bpf: Introduce kprobe_multi session attach Andrii Nakryiko
2024-04-24 5:12 ` John Fastabend
2024-04-24 11:43 ` Jiri Olsa
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=ZijwsrKWCbo57vUE@krava \
--to=olsajiri@gmail.com \
--cc=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=kafai@fb.com \
--cc=kpsingh@chromium.org \
--cc=mhiramat@kernel.org \
--cc=sdf@google.com \
--cc=songliubraving@fb.com \
--cc=vmalik@redhat.com \
--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).