From: Lorenzo Bianconi <lorenzo.bianconi@redhat.com>
To: Yonghong Song <yhs@fb.com>
Cc: Lorenzo Bianconi <lorenzo@kernel.org>,
bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
brouer@redhat.com, toke@redhat.com, andrii@kernel.org,
netdev@vger.kernel.org
Subject: Re: [PATCH bpf-next] selftest/bpf: check invalid length in test_xdp_update_frags
Date: Fri, 4 Feb 2022 18:52:04 +0100 [thread overview]
Message-ID: <Yf1nxMWEWy4DSwgN@lore-desk> (raw)
In-Reply-To: <c3858f6b-43d5-18ef-2fc8-b58c13c12b05@fb.com>
[-- Attachment #1: Type: text/plain, Size: 2859 bytes --]
>
>
> On 2/4/22 5:58 AM, Lorenzo Bianconi wrote:
> > Update test_xdp_update_frags adding a test for a buffer size
> > set to (MAX_SKB_FRAGS + 2) * PAGE_SIZE. The kernel is supposed
> > to return -ENOMEM.
> >
> > Signed-off-by: Lorenzo Bianconi <lorenzo@kernel.org>
> > ---
> > .../bpf/prog_tests/xdp_adjust_frags.c | 37 ++++++++++++++++++-
> > 1 file changed, 36 insertions(+), 1 deletion(-)
> >
> > diff --git a/tools/testing/selftests/bpf/prog_tests/xdp_adjust_frags.c b/tools/testing/selftests/bpf/prog_tests/xdp_adjust_frags.c
> > index 134d0ac32f59..61d5b585eb15 100644
> > --- a/tools/testing/selftests/bpf/prog_tests/xdp_adjust_frags.c
> > +++ b/tools/testing/selftests/bpf/prog_tests/xdp_adjust_frags.c
> > @@ -5,11 +5,12 @@
> > void test_xdp_update_frags(void)
> > {
> > const char *file = "./test_xdp_update_frags.o";
> > + int err, prog_fd, max_skb_frags, buf_size, num;
> > struct bpf_program *prog;
> > struct bpf_object *obj;
> > - int err, prog_fd;
> > __u32 *offset;
> > __u8 *buf;
> > + FILE *f;
> > LIBBPF_OPTS(bpf_test_run_opts, topts);
> > obj = bpf_object__open(file);
> > @@ -99,6 +100,40 @@ void test_xdp_update_frags(void)
> > ASSERT_EQ(buf[7621], 0xbb, "xdp_update_frag buf[7621]");
> > free(buf);
> > +
> > + /* test_xdp_update_frags: unsupported buffer size */
> > + f = fopen("/proc/sys/net/core/max_skb_frags", "r");
> > + if (!ASSERT_OK_PTR(f, "max_skb_frag file pointer"))
> > + goto out;
>
> In kernel, the nr_frags checking is against MAX_SKB_FRAGS,
> but if /proc/sys/net/core/max_skb_flags is 2 or more less
> than MAX_SKB_FRAGS, the test won't fail, right?
yes, you are right. Should we use the same definition used in
include/linux/skbuff.h instead? Something like:
if (65536 / page_size + 1 < 16)
max_skb_flags = 16;
else
max_skb_flags = 65536/page_size + 1;
Regards,
Lorenzo
>
> > +
> > + num = fscanf(f, "%d", &max_skb_frags);
> > + fclose(f);
> > +
> > + if (!ASSERT_EQ(num, 1, "max_skb_frags read failed"))
> > + goto out;
> > +
> > + /* xdp_buff linear area size is always set to 4096 in the
> > + * bpf_prog_test_run_xdp routine.
> > + */
> > + buf_size = 4096 + (max_skb_frags + 1) * sysconf(_SC_PAGE_SIZE);
> > + buf = malloc(buf_size);
> > + if (!ASSERT_OK_PTR(buf, "alloc buf"))
> > + goto out;
> > +
> > + memset(buf, 0, buf_size);
> > + offset = (__u32 *)buf;
> > + *offset = 16;
> > + buf[*offset] = 0xaa;
> > + buf[*offset + 15] = 0xaa;
> > +
> > + topts.data_in = buf;
> > + topts.data_out = buf;
> > + topts.data_size_in = buf_size;
> > + topts.data_size_out = buf_size;
> > +
> > + err = bpf_prog_test_run_opts(prog_fd, &topts);
> > + ASSERT_EQ(err, -ENOMEM, "unsupported buffer size");
> > + free(buf);
> > out:
> > bpf_object__close(obj);
> > }
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2022-02-04 17:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-04 13:58 [PATCH bpf-next] selftest/bpf: check invalid length in test_xdp_update_frags Lorenzo Bianconi
2022-02-04 17:37 ` Yonghong Song
2022-02-04 17:52 ` Lorenzo Bianconi [this message]
2022-02-04 18:14 ` Yonghong Song
2022-02-04 18:30 ` Lorenzo Bianconi
2022-02-04 19:08 ` Lorenzo Bianconi
2022-02-07 17:08 ` Yonghong Song
2022-02-07 17:53 ` Lorenzo Bianconi
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=Yf1nxMWEWy4DSwgN@lore-desk \
--to=lorenzo.bianconi@redhat.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=brouer@redhat.com \
--cc=daniel@iogearbox.net \
--cc=lorenzo@kernel.org \
--cc=netdev@vger.kernel.org \
--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).