From: Jiri Olsa <jolsa@redhat.com>
To: Song Liu <songliubraving@fb.com>
Cc: "Jiri Olsa" <jolsa@kernel.org>,
"Alexei Starovoitov" <ast@kernel.org>,
"Daniel Borkmann" <daniel@iogearbox.net>,
"Andrii Nakryiko" <andriin@fb.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"bpf@vger.kernel.org" <bpf@vger.kernel.org>,
"Martin Lau" <kafai@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: [RFC PATCH bpf-next 2/4] selftests/bpf: Add re-attach test to fentry_test
Date: Tue, 30 Mar 2021 22:02:35 +0200 [thread overview]
Message-ID: <YGOD2xtqR+zMw0o8@krava> (raw)
In-Reply-To: <A0B730F5-758F-4F28-9543-4ED08F0BDECB@fb.com>
On Tue, Mar 30, 2021 at 01:23:15AM +0000, Song Liu wrote:
>
>
> > On Mar 28, 2021, at 4:26 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>
> >
> [...]
> > +
> > +void test_fentry_test(void)
> > +{
> > + struct fentry_test *fentry_skel = NULL;
> > + struct bpf_link *link;
> > + 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__attach(fentry_skel);
> > + if (CHECK(err, "fentry_attach", "fentry attach failed: %d\n", err))
> > + goto cleanup;
> > +
> > + err = fentry_test(fentry_skel);
> > + if (CHECK(err, "fentry_test", "fentry test failed: %d\n", err))
> > + goto cleanup;
> > +
> > + fentry_test__detach(fentry_skel);
> > +
> > + /* Re-attach and test again */
> > + err = fentry_test__attach(fentry_skel);
> > + if (CHECK(err, "fentry_attach", "fentry re-attach failed: %d\n", err))
> > + goto cleanup;
> > +
> > + link = bpf_program__attach(fentry_skel->progs.test1);
> > + if (CHECK(!IS_ERR(link), "attach_fentry re-attach without detach",
> > + "err: %ld\n", PTR_ERR(link)))
>
> nit: I guess we shouldn't print PTR_ERR(link) when link is not an error code?
> This shouldn't break though.
true, makes no sense.. I'll remove it
thanks,
jirka
next prev parent reply other threads:[~2021-03-30 20:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-28 11:26 [RFC PATCH bpf-next 0/4] bpf: Tracing programs re-attach Jiri Olsa
2021-03-28 11:26 ` [RFC PATCH bpf-next 1/4] bpf: Allow trampoline re-attach Jiri Olsa
2021-03-30 1:18 ` Song Liu
2021-04-03 11:24 ` Toke Høiland-Jørgensen
2021-04-03 18:21 ` Alexei Starovoitov
2021-04-05 14:08 ` Jiri Olsa
2021-04-05 14:15 ` Toke Høiland-Jørgensen
2021-04-05 21:58 ` Jiri Olsa
2021-04-05 14:06 ` Jiri Olsa
2021-03-28 11:26 ` [RFC PATCH bpf-next 2/4] selftests/bpf: Add re-attach test to fentry_test Jiri Olsa
2021-03-30 1:23 ` Song Liu
2021-03-30 20:02 ` Jiri Olsa [this message]
2021-03-28 11:26 ` [RFC PATCH bpf-next 3/4] selftests/bpf: Add re-attach test to fexit_test Jiri Olsa
2021-03-28 11:26 ` [RFC PATCH bpf-next 4/4] selftests/bpf: Test that module can't be unloaded with attached trampoline Jiri Olsa
2021-03-30 6:12 ` Song Liu
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=YGOD2xtqR+zMw0o8@krava \
--to=jolsa@redhat.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).