From: Jiri Olsa <jolsa@redhat.com>
To: Andrii Nakryiko <andrii.nakryiko@gmail.com>
Cc: "Jiri Olsa" <jolsa@kernel.org>,
"Alexei Starovoitov" <ast@kernel.org>,
"Daniel Borkmann" <daniel@iogearbox.net>,
"Andrii Nakryiko" <andriin@fb.com>,
Networking <netdev@vger.kernel.org>, bpf <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>,
"Toke Høiland-Jørgensen" <toke@redhat.com>
Subject: Re: [PATCHv2 bpf-next 2/5] selftests/bpf: Add re-attach test to fentry_test
Date: Thu, 8 Apr 2021 13:52:18 +0200 [thread overview]
Message-ID: <YG7uckNf7skULOCN@krava> (raw)
In-Reply-To: <CAEf4Bzagf5H31H8uSuMiVDpE5a6tgDOsZkJdmMK0hGhVDADRHQ@mail.gmail.com>
On Wed, Apr 07, 2021 at 03:47:30PM -0700, Andrii Nakryiko wrote:
> On Wed, Apr 7, 2021 at 4:21 AM Jiri Olsa <jolsa@kernel.org> wrote:
> >
> > Adding the test to re-attach (detach/attach again) tracing
> > fentry programs, plus check that already linked program can't
> > be attached again.
> >
> > Fixing the number of check-ed results, which should be 8.
> >
> > Signed-off-by: Jiri Olsa <jolsa@kernel.org>
> > ---
> > .../selftests/bpf/prog_tests/fentry_test.c | 48 +++++++++++++++----
> > 1 file changed, 38 insertions(+), 10 deletions(-)
> >
> > diff --git a/tools/testing/selftests/bpf/prog_tests/fentry_test.c b/tools/testing/selftests/bpf/prog_tests/fentry_test.c
> > index 04ebbf1cb390..1f7566e772e9 100644
> > --- a/tools/testing/selftests/bpf/prog_tests/fentry_test.c
> > +++ b/tools/testing/selftests/bpf/prog_tests/fentry_test.c
> > @@ -3,20 +3,24 @@
> > #include <test_progs.h>
> > #include "fentry_test.skel.h"
> >
> > -void test_fentry_test(void)
> > +static __u32 duration;
> > +
> > +static int fentry_test(struct fentry_test *fentry_skel)
> > {
> > - struct fentry_test *fentry_skel = NULL;
> > + struct bpf_link *link;
> > int err, prog_fd, i;
> > - __u32 duration = 0, retval;
> > __u64 *result;
> > -
> > - fentry_skel = fentry_test__open_and_load();
> > - if (CHECK(!fentry_skel, "fentry_skel_load", "fentry skeleton failed\n"))
> > - goto cleanup;
> > + __u32 retval;
> >
> > err = fentry_test__attach(fentry_skel);
> > if (CHECK(err, "fentry_attach", "fentry attach failed: %d\n", err))
> > - goto cleanup;
> > + return err;
> > +
> > + /* Check that already linked program can't be attached again. */
> > + link = bpf_program__attach(fentry_skel->progs.test1);
> > + if (CHECK(!IS_ERR(link), "fentry_attach_link",
>
> if (!ASSERT_ERR_PTR(link, "fentry_attach_link")) ?
ok
>
> > + "re-attach without detach should not succeed"))
> > + return -1;
> >
> > prog_fd = bpf_program__fd(fentry_skel->progs.test1);
> > err = bpf_prog_test_run(prog_fd, 1, NULL, 0,
> > @@ -26,12 +30,36 @@ void test_fentry_test(void)
> > err, errno, retval, duration);
> >
> > result = (__u64 *)fentry_skel->bss;
> > - for (i = 0; i < 6; i++) {
> > + for (i = 0; i < 8; i++) {
>
> how about using sizeof(*fentry_skel->bss) / sizeof(__u64) ?
ok
>
> > if (CHECK(result[i] != 1, "result",
> > "fentry_test%d failed err %lld\n", i + 1, result[i]))
> > - goto cleanup;
> > + return -1;
> > }
> >
> > + fentry_test__detach(fentry_skel);
> > +
> > + /* zero results for re-attach test */
> > + for (i = 0; i < 8; i++)
> > + result[i] = 0;
> > + return 0;
> > +}
> > +
> > +void test_fentry_test(void)
> > +{
> > + struct fentry_test *fentry_skel = NULL;
> > + int err;
> > +
> > + fentry_skel = fentry_test__open_and_load();
> > + if (CHECK(!fentry_skel, "fentry_skel_load", "fentry skeleton failed\n"))
> > + goto cleanup;
> > +
> > + err = fentry_test(fentry_skel);
> > + if (CHECK(err, "fentry_test", "first attach failed\n"))
> > + goto cleanup;
> > +
> > + err = fentry_test(fentry_skel);
> > + CHECK(err, "fentry_test", "second attach failed\n");
>
> overall: please try to use ASSERT_xxx macros, they are easier to
> follow and require less typing
ok, will check
thanks,
jirka
next prev parent reply other threads:[~2021-04-08 11:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-06 21:29 [PATCHv2 bpf-next 0/5] bpf: Tracing and lsm programs re-attach Jiri Olsa
2021-04-06 21:29 ` [PATCHv2 bpf-next 1/5] bpf: Allow trampoline re-attach for tracing and lsm programs Jiri Olsa
2021-04-06 21:35 ` Toke Høiland-Jørgensen
2021-04-06 21:29 ` [PATCHv2 bpf-next 2/5] selftests/bpf: Add re-attach test to fentry_test Jiri Olsa
2021-04-07 22:47 ` Andrii Nakryiko
2021-04-08 11:52 ` Jiri Olsa [this message]
2021-04-06 21:29 ` [PATCHv2 bpf-next 3/5] selftests/bpf: Add re-attach test to fexit_test Jiri Olsa
2021-04-07 22:51 ` Andrii Nakryiko
2021-04-08 11:51 ` Jiri Olsa
2021-04-06 21:29 ` [PATCHv2 bpf-next 4/5] selftests/bpf: Add re-attach test to lsm test Jiri Olsa
2021-04-06 21:29 ` [PATCHv2 bpf-next 5/5] selftests/bpf: Test that module can't be unloaded with attached trampoline Jiri Olsa
2021-04-07 23:04 ` Andrii Nakryiko
2021-04-08 11:59 ` 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=YG7uckNf7skULOCN@krava \
--to=jolsa@redhat.com \
--cc=andrii.nakryiko@gmail.com \
--cc=andriin@fb.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kafai@fb.com \
--cc=kpsingh@chromium.org \
--cc=netdev@vger.kernel.org \
--cc=songliubraving@fb.com \
--cc=toke@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).