From: John Fastabend <john.fastabend@gmail.com>
To: Jakub Sitnicki <jakub@cloudflare.com>,
John Fastabend <john.fastabend@gmail.com>
Cc: bpf@vger.kernel.org, netdev@vger.kernel.org, andrii@kernel.org
Subject: Re: [PATCH bpf-next v2 2/4] bpf: sockmap, add a sendmsg test so we can check that path
Date: Fri, 26 Jan 2024 07:38:26 -0800 [thread overview]
Message-ID: <65b3d1f2d5333_154997208d0@john.notmuch> (raw)
In-Reply-To: <87zfwse0ln.fsf@cloudflare.com>
Jakub Sitnicki wrote:
> On Wed, Jan 24, 2024 at 10:54 AM -08, John Fastabend wrote:
> > Sendmsg path with multiple buffers is slightly different from a single
> > send in how we have to handle and walk the sg when doing pops. Lets
> > ensure this walk is correct.
> >
> > Signed-off-by: John Fastabend <john.fastabend@gmail.com>
> > ---
> > .../bpf/prog_tests/sockmap_helpers.h | 8 +++
> > .../bpf/prog_tests/sockmap_msg_helpers.c | 53 +++++++++++++++++++
> > 2 files changed, 61 insertions(+)
> >
> > diff --git a/tools/testing/selftests/bpf/prog_tests/sockmap_helpers.h b/tools/testing/selftests/bpf/prog_tests/sockmap_helpers.h
> > index 781cbdf01d7b..4d8d24482032 100644
> > --- a/tools/testing/selftests/bpf/prog_tests/sockmap_helpers.h
> > +++ b/tools/testing/selftests/bpf/prog_tests/sockmap_helpers.h
> > @@ -103,6 +103,14 @@
> > __ret; \
> > })
> >
> > +#define xsendmsg(fd, msg, flags) \
> > + ({ \
> > + ssize_t __ret = sendmsg((fd), (msg), (flags)); \
> > + if (__ret == -1) \
> > + FAIL_ERRNO("sendmsg"); \
> > + __ret; \
> > + })
> > +
> > #define xrecv_nonblock(fd, buf, len, flags) \
> > ({ \
> > ssize_t __ret = recv_timeout((fd), (buf), (len), (flags), \
> > diff --git a/tools/testing/selftests/bpf/prog_tests/sockmap_msg_helpers.c b/tools/testing/selftests/bpf/prog_tests/sockmap_msg_helpers.c
> > index 9ffe02f45808..e5e618e84950 100644
> > --- a/tools/testing/selftests/bpf/prog_tests/sockmap_msg_helpers.c
> > +++ b/tools/testing/selftests/bpf/prog_tests/sockmap_msg_helpers.c
> > @@ -52,6 +52,50 @@ static void pop_simple_send(struct msg_test_opts *opts, int start, int len)
> > ASSERT_OK(cmp, "pop cmp end bytes failed");
> > }
> >
> > +static void pop_complex_send(struct msg_test_opts *opts, int start, int len)
> > +{
> > + struct test_sockmap_msg_helpers *skel = opts->skel;
> > + char buf[] = "abcdefghijklmnopqrstuvwxyz";
> > + size_t sent, recv, total = 0;
> > + struct msghdr msg = {0};
> > + struct iovec iov[15];
> > + char *recvbuf;
> > + int i;
> > +
> > + for (i = 0; i < 15; i++) {
>
> Always nice to use ARRAY_SIZE.
Agree will do.
>
> > + iov[i].iov_base = buf;
> > + iov[i].iov_len = sizeof(buf);
> > + total += sizeof(buf);
> > + }
> > +
> > + recvbuf = malloc(total);
> > + if (!recvbuf)
> > + FAIL("pop complex send malloc failure\n");
>
> 390 bytes, why not have it on stack?
Sure one less thing that could fail seems like a win.
next prev parent reply other threads:[~2024-01-26 15:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-24 18:53 [PATCH bpf-next v2 0/4] transition sockmap testing to test_progs John Fastabend
2024-01-24 18:54 ` [PATCH bpf-next v2 1/4] bpf: sockmap, add test for sk_msg prog pop msg helper John Fastabend
2024-01-26 11:48 ` Jakub Sitnicki
2024-01-26 15:37 ` John Fastabend
2024-01-24 18:54 ` [PATCH bpf-next v2 2/4] bpf: sockmap, add a sendmsg test so we can check that path John Fastabend
2024-01-26 12:17 ` Jakub Sitnicki
2024-01-26 14:24 ` Jakub Sitnicki
2024-01-26 15:38 ` John Fastabend [this message]
2024-01-24 18:54 ` [PATCH bpf-next v2 3/4] bpf: sockmap, add a cork to force buffering of the scatterlist John Fastabend
2024-01-26 14:19 ` Jakub Sitnicki
2024-01-26 15:38 ` John Fastabend
2024-01-24 18:54 ` [PATCH bpf-next v2 4/4] bpf: sockmap test cork and pop combined John Fastabend
2024-01-24 22:58 ` [PATCH bpf-next v2 0/4] transition sockmap testing to test_progs John Fastabend
2024-01-26 14:39 ` Jakub Sitnicki
2024-01-26 15:40 ` John Fastabend
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=65b3d1f2d5333_154997208d0@john.notmuch \
--to=john.fastabend@gmail.com \
--cc=andrii@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=jakub@cloudflare.com \
--cc=netdev@vger.kernel.org \
/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.