From: Breno Leitao <[email protected]>
To: Martin KaFai Lau <[email protected]>
Cc: "Alexei Starovoitov" <[email protected]>,
"Daniel Borkmann" <[email protected]>,
[email protected], [email protected],
[email protected], [email protected],
[email protected], [email protected], [email protected],
"Wang Yufen" <[email protected]>,
"Daniel Müller" <[email protected]>,
"open list:KERNEL SELFTEST FRAMEWORK"
<[email protected]>,
[email protected], [email protected], [email protected],
[email protected],
"Andrii Nakryiko" <[email protected]>,
"Mykola Lysenko" <[email protected]>, "Song Liu" <[email protected]>,
"Yonghong Song" <[email protected]>,
"John Fastabend" <[email protected]>,
"KP Singh" <[email protected]>, "Hao Luo" <[email protected]>,
"Jiri Olsa" <[email protected]>, "Shuah Khan" <[email protected]>
Subject: Re: [PATCH v3 9/9] selftests/bpf/sockopt: Add io_uring support
Date: Fri, 25 Aug 2023 07:15:05 -0700 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On Mon, Aug 21, 2023 at 01:59:12PM -0700, Martin KaFai Lau wrote:
> On 8/17/23 7:55 AM, Breno Leitao wrote:
> > diff --git a/tools/testing/selftests/bpf/Makefile b/tools/testing/selftests/bpf/Makefile
> > index 538df8fb8c42..4da04242b848 100644
> > --- a/tools/testing/selftests/bpf/Makefile
> > +++ b/tools/testing/selftests/bpf/Makefile
> > @@ -362,6 +362,7 @@ CLANG_CFLAGS = $(CLANG_SYS_INCLUDES) \
> > $(OUTPUT)/test_l4lb_noinline.o: BPF_CFLAGS += -fno-inline
> > $(OUTPUT)/test_xdp_noinline.o: BPF_CFLAGS += -fno-inline
> > +$(OUTPUT)/test_progs.o: CFLAGS += -I../../../include/
>
> This is the tools/include? Is it really needed? iirc, some of the
> prog_tests/*.c has already been using files from tools/include.
You are right, we don't need it.
> > $(OUTPUT)/flow_dissector_load.o: flow_dissector_load.h
> > $(OUTPUT)/cgroup_getset_retval_hooks.o: cgroup_getset_retval_hooks.h
> > diff --git a/tools/testing/selftests/bpf/prog_tests/sockopt.c b/tools/testing/selftests/bpf/prog_tests/sockopt.c
> > index 9e6a5e3ed4de..4693ad8bfe8f 100644
> > --- a/tools/testing/selftests/bpf/prog_tests/sockopt.c
> > +++ b/tools/testing/selftests/bpf/prog_tests/sockopt.c
> > @@ -1,5 +1,6 @@
> > // SPDX-License-Identifier: GPL-2.0
> > #include <test_progs.h>
> > +#include <io_uring/mini_liburing.h>
> > #include "cgroup_helpers.h"
> > static char bpf_log_buf[4096];
> > @@ -38,6 +39,7 @@ static struct sockopt_test {
> > socklen_t get_optlen_ret;
> > enum sockopt_test_error error;
> > + bool io_uring_support;
> > } tests[] = {
> > /* ==================== getsockopt ==================== */
> > @@ -53,6 +55,7 @@ static struct sockopt_test {
> > .attach_type = BPF_CGROUP_GETSOCKOPT,
> > .expected_attach_type = 0,
> > .error = DENY_LOAD,
> > + .io_uring_support = true,
>
> DENY_LOAD probably won't be an intersting test. The set/getsockopt won't be called.
Yea, I will remove all the DENY_LOAD and DENY_ATTACH tests.
> The existing test does not seem to have SOL_SOCKET for getsockopt also.
I am planning to move two tests to use SOL_SOCKET so we can also
exercise the io_uring tests. This is what I have in mind right now:
* getsockopt: read ctx->optlen
* getsockopt: support smaller ctx->optlen
> > -static int run_test(int cgroup_fd, struct sockopt_test *test)
> > +/* Core function that handles io_uring ring initialization,
> > + * sending SQE with sockopt command and waiting for the CQE.
> > + */
> > +static int uring_sockopt(int op, int fd, int level, int optname,
> > + const void *optval, socklen_t optlen)
> > +{
> > + struct io_uring_cqe *cqe;
> > + struct io_uring_sqe *sqe;
> > + struct io_uring ring;
> > + int err;
> > +
> > + err = io_uring_queue_init(1, &ring, 0);
> > + if (err) {
> > + log_err("Failed to initialize io_uring ring");
> > + return err;
> > + }
> > +
> > + sqe = io_uring_get_sqe(&ring);
> > + if (!sqe) {
> > + log_err("Failed to get an SQE");
> > + return -1;
>
> No need to io_uring_queue_exit() on the error path?
Good idea. updating it.
> > + }
> > +
> > + io_uring_prep_cmd(sqe, op, fd, level, optname, optval, optlen);
> > +
> > + err = io_uring_submit(&ring);
> > + if (err != 1) {
> > + log_err("Failed to submit SQE");
>
> Use ASSERT_* instead.
>
> Regarding how to land this set,
> it will be useful to have the selftest running in the bpf CI. While there is
> iouring changes, some of the changes is in bpf and/or netdev also. eg. Patch
> 3 already has a conflict with the net-next and bpf-next tree because of a
> recent commit in socket.c on Aug 9.
>
> May be Alexi and Daniel can advise how was similar patch managed before ?
>
>
prev parent reply other threads:[~2023-08-25 14:17 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-17 14:55 [PATCH v3 0/9] io_uring: Initial support for {s,g}etsockopt commands Breno Leitao
2023-08-17 14:55 ` [PATCH v3 1/9] bpf: Leverage sockptr_t in BPF getsockopt hook Breno Leitao
2023-08-17 14:55 ` [PATCH v3 2/9] bpf: Leverage sockptr_t in BPF setsockopt hook Breno Leitao
2023-08-17 14:55 ` [PATCH v3 3/9] net/socket: Break down __sys_setsockopt Breno Leitao
2023-08-19 14:35 ` Willem de Bruijn
2023-08-17 14:55 ` [PATCH v3 4/9] io_uring/cmd: Pass compat mode in issue_flags Breno Leitao
2023-08-17 14:55 ` [PATCH v3 5/9] selftests/net: Extract uring helpers to be reusable Breno Leitao
2023-08-17 14:55 ` [PATCH v3 6/9] io_uring/cmd: Introduce SOCKET_URING_OP_GETSOCKOPT Breno Leitao
2023-08-17 18:38 ` Gabriel Krisman Bertazi
2023-08-21 9:09 ` Breno Leitao
2023-08-21 14:52 ` Gabriel Krisman Bertazi
2023-08-17 14:55 ` [PATCH v3 7/9] io_uring/cmd: Introduce SOCKET_URING_OP_SETSOCKOPT Breno Leitao
2023-08-17 14:55 ` [PATCH v3 8/9] io_uring/cmd: BPF hook for getsockopt cmd Breno Leitao
2023-08-17 19:08 ` Gabriel Krisman Bertazi
2023-08-21 9:14 ` Breno Leitao
2023-08-21 17:03 ` Gabriel Krisman Bertazi
2023-08-23 13:48 ` Breno Leitao
2023-08-22 13:50 ` David Laight
2023-08-21 20:25 ` Martin KaFai Lau
2023-08-25 16:53 ` Breno Leitao
2023-08-26 0:45 ` Martin KaFai Lau
2023-08-17 14:55 ` [PATCH v3 9/9] selftests/bpf/sockopt: Add io_uring support Breno Leitao
2023-08-21 20:59 ` Martin KaFai Lau
2023-08-25 14:15 ` Breno Leitao [this message]
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 \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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