All of lore.kernel.org
 help / color / mirror / Atom feed
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>,
	"Julia Lawall" <julia.lawall@inria.fr>
Subject: Re: [PATCHv4 bpf-next 2/5] selftests/bpf: Add re-attach test to fentry_test
Date: Wed, 14 Apr 2021 12:56:59 +0200	[thread overview]
Message-ID: <YHbKexxx+jyMeVnM@krava> (raw)
In-Reply-To: <CAEf4Bza6OXC4aVuxVGnn-DOANuFbnuJ++=q8fFpD-f48kb7_pw@mail.gmail.com>

On Tue, Apr 13, 2021 at 02:54:10PM -0700, Andrii Nakryiko wrote:

SNIP

> >         __u32 duration = 0, retval;
> > +       struct bpf_link *link;
> >         __u64 *result;
> >
> > -       fentry_skel = fentry_test__open_and_load();
> > -       if (CHECK(!fentry_skel, "fentry_skel_load", "fentry skeleton failed\n"))
> > -               goto cleanup;
> > -
> >         err = fentry_test__attach(fentry_skel);
> > -       if (CHECK(err, "fentry_attach", "fentry attach failed: %d\n", err))
> > -               goto cleanup;
> > +       if (!ASSERT_OK(err, "fentry_attach"))
> > +               return err;
> > +
> > +       /* Check that already linked program can't be attached again. */
> > +       link = bpf_program__attach(fentry_skel->progs.test1);
> > +       if (!ASSERT_ERR_PTR(link, "fentry_attach_link"))
> > +               return -1;
> >
> >         prog_fd = bpf_program__fd(fentry_skel->progs.test1);
> >         err = bpf_prog_test_run(prog_fd, 1, NULL, 0,
> >                                 NULL, NULL, &retval, &duration);
> > -       CHECK(err || retval, "test_run",
> > -             "err %d errno %d retval %d duration %d\n",
> > -             err, errno, retval, duration);
> > +       ASSERT_OK(err || retval, "test_run");
> 
> this is quite misleading, even if will result in a correct check. Toke
> did this in his patch set:
> 
> ASSERT_OK(err, ...);
> ASSERT_EQ(retval, 0, ...);
> 
> It is a better and more straightforward way to validate the checks
> instead of relying on (err || retval) -> bool (true) -> int (1) -> !=
> 0 chain.

ok, makes sense

SNIP

> > +void test_fentry_test(void)
> > +{
> > +       struct fentry_test *fentry_skel = NULL;
> > +       int err;
> > +
> > +       fentry_skel = fentry_test__open_and_load();
> > +       if (!ASSERT_OK_PTR(fentry_skel, "fentry_skel_load"))
> > +               goto cleanup;
> > +
> > +       err = fentry_test(fentry_skel);
> > +       if (!ASSERT_OK(err, "fentry_first_attach"))
> > +               goto cleanup;
> > +
> > +       err = fentry_test(fentry_skel);
> > +       ASSERT_OK(err, "fentry_second_attach");
> > +
> >  cleanup:
> >         fentry_test__destroy(fentry_skel);
> >  }
> > diff --git a/tools/testing/selftests/bpf/test_progs.h b/tools/testing/selftests/bpf/test_progs.h
> > index e87c8546230e..ee7e3b45182a 100644
> > --- a/tools/testing/selftests/bpf/test_progs.h
> > +++ b/tools/testing/selftests/bpf/test_progs.h
> > @@ -210,7 +210,7 @@ extern int test__join_cgroup(const char *path);
> >  #define ASSERT_ERR_PTR(ptr, name) ({                                   \
> >         static int duration = 0;                                        \
> >         const void *___res = (ptr);                                     \
> > -       bool ___ok = IS_ERR(___res)                                     \
> > +       bool ___ok = IS_ERR(___res);                                    \
> 
> heh, it probably deserves a separate patch with Fixes tag...

va bene

jirka


  reply	other threads:[~2021-04-14 10:57 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-12 16:24 [PATCHv4 bpf-next 0/5] bpf: Tracing and lsm programs re-attach Jiri Olsa
2021-04-12 16:24 ` [PATCHv4 bpf-next 1/5] bpf: Allow trampoline re-attach for tracing and lsm programs Jiri Olsa
2021-04-13 22:03   ` Andrii Nakryiko
2021-04-14 11:01     ` Jiri Olsa
2021-04-12 16:24 ` [PATCHv4 bpf-next 2/5] selftests/bpf: Add re-attach test to fentry_test Jiri Olsa
2021-04-13 21:54   ` Andrii Nakryiko
2021-04-14 10:56     ` Jiri Olsa [this message]
2021-04-14 22:18       ` Andrii Nakryiko
2021-04-12 16:25 ` [PATCHv4 bpf-next 3/5] selftests/bpf: Add re-attach test to fexit_test Jiri Olsa
2021-04-13 21:55   ` Andrii Nakryiko
2021-04-14 11:01     ` Jiri Olsa
2021-04-12 16:25 ` [PATCHv4 bpf-next 4/5] selftests/bpf: Add re-attach test to lsm test Jiri Olsa
2021-04-13 21:57   ` Andrii Nakryiko
2021-04-14 10:54     ` Jiri Olsa
2021-04-12 16:25 ` [PATCHv4 bpf-next 5/5] selftests/bpf: Test that module can't be unloaded with attached trampoline 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=YHbKexxx+jyMeVnM@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=julia.lawall@inria.fr \
    --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 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.