From: David Vernet <void@manifault.com>
To: Andrii Nakryiko <andrii.nakryiko@gmail.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
daniel@iogearbox.net, kernel-team@fb.com, 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, joannelkoong@gmail.com, tj@kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 4/4] selftests/bpf: Add selftests validating the user ringbuf
Date: Tue, 30 Aug 2022 08:46:12 -0500 [thread overview]
Message-ID: <Yw4UpK4uPZP9fYD+@maniforge.dhcp.thefacebook.com> (raw)
In-Reply-To: <CAEf4Bzbj0ACUmZqQLhRR5DvEX9Zphqz5UwBWdkTdXfKqxWM0mQ@mail.gmail.com>
On Wed, Aug 24, 2022 at 03:03:54PM -0700, Andrii Nakryiko wrote:
[...]
> > + CHECK(read <= 0, "snprintf_comm",
> > + "Failed to write index %d to comm\n", i);
>
> please, no CHECK() use in new tests, we have ASSERT_xxx() covering all
> common cases
No problem, I'll make this change in v4. Unless I missed something,
CHECK() isn't documented as deprecated in test_progs.h. I'll take care
of adding that in a separate change.
> > +static long
> > +bad_access1(struct bpf_dynptr *dynptr, void *context)
> > +{
> > + const struct sample *sample;
> > +
> > + sample = bpf_dynptr_data(dynptr - 1, 0, sizeof(*sample));
> > + bpf_printk("Was able to pass bad pointer %lx\n", (__u64)dynptr - 1);
> > +
> > + return 0;
> > +}
> > +
> > +/* A callback that accesses a dynptr in a bpf_user_ringbuf_drain callback should
> > + * not be able to read before the pointer.
> > + */
> > +SEC("?raw_tp/sys_nanosleep")
>
> there is no sys_nanosleep raw tracepoint, use SEC("?raw_tp") to
> specify type, that's enough
Got it, thanks for catching that. Will fix.
> > diff --git a/tools/testing/selftests/bpf/test_user_ringbuf.h b/tools/testing/selftests/bpf/test_user_ringbuf.h
> > new file mode 100644
> > index 000000000000..1643b4d59ba7
> > --- /dev/null
> > +++ b/tools/testing/selftests/bpf/test_user_ringbuf.h
>
> nit: I'd probably put it under progs/test_user_ringbuf.h so it's
> closer to BPF source code. As it is right now, it's neither near
> user-space part of tests nor near BPF part.
Fair enough, will fix.
Thanks,
David
next prev parent reply other threads:[~2022-08-30 13:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-18 22:12 [PATCH v3 0/4] bpf: Add user-space-publisher ringbuffer map type David Vernet
2022-08-18 22:12 ` [PATCH v3 1/4] bpf: Define new BPF_MAP_TYPE_USER_RINGBUF " David Vernet
2022-08-24 20:52 ` Andrii Nakryiko
2022-08-18 22:12 ` [PATCH v3 2/4] bpf: Add bpf_user_ringbuf_drain() helper David Vernet
2022-08-24 21:22 ` Andrii Nakryiko
2022-08-30 13:28 ` David Vernet
2022-09-09 22:45 ` Andrii Nakryiko
2022-08-18 22:12 ` [PATCH v3 3/4] bpf: Add libbpf logic for user-space ring buffer David Vernet
2022-08-24 21:58 ` Andrii Nakryiko
2022-08-30 13:42 ` David Vernet
2022-09-09 22:50 ` Andrii Nakryiko
2022-08-18 22:12 ` [PATCH v3 4/4] selftests/bpf: Add selftests validating the user ringbuf David Vernet
2022-08-24 22:03 ` Andrii Nakryiko
2022-08-30 13:46 ` David Vernet [this message]
2022-08-24 17:38 ` [PATCH v3 0/4] bpf: Add user-space-publisher ringbuffer map type Daniel Borkmann
2022-08-30 13:50 ` David Vernet
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=Yw4UpK4uPZP9fYD+@maniforge.dhcp.thefacebook.com \
--to=void@manifault.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=joannelkoong@gmail.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kernel-team@fb.com \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=sdf@google.com \
--cc=song@kernel.org \
--cc=tj@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