From: Martin KaFai Lau <martin.lau@linux.dev>
To: Geliang Tang <geliang@kernel.org>
Cc: Andrii Nakryiko <andrii@kernel.org>,
Eduard Zingerman <eddyz87@gmail.com>,
Mykola Lysenko <mykolal@fb.com>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Song Liu <song@kernel.org>,
Yonghong Song <yonghong.song@linux.dev>,
John Fastabend <john.fastabend@gmail.com>,
KP Singh <kpsingh@kernel.org>, Hao Luo <haoluo@google.com>,
Jiri Olsa <jolsa@kernel.org>, Shuah Khan <shuah@kernel.org>,
Geliang Tang <tanggeliang@kylinos.cn>,
bpf@vger.kernel.org, linux-kselftest@vger.kernel.org,
Martin KaFai Lau <martin.lau@kernel.org>
Subject: Re: [PATCH bpf-next v2 2/5] selftests/bpf: Drop must_fail from network_helper_opts
Date: Fri, 12 Jul 2024 10:36:36 -0700 [thread overview]
Message-ID: <2cf71a18-b2f2-477b-85fb-25a907b8dd73@linux.dev> (raw)
In-Reply-To: <5730eabdd6e90d1534d4f5df47e55a76f04197ca.1720767414.git.tanggeliang@kylinos.cn>
On 7/12/24 12:04 AM, Geliang Tang wrote:
> From: Geliang Tang <tanggeliang@kylinos.cn>
>
> The struct member "must_fail" of network_helper_opts() is only used in
> cgroup_v1v2 tests, it makes sense to drop it from network_helper_opts.
>
> Return value (fd) of connect_to_fd_opts() and the expect errno (EPERM)
> can be checked in cgroup_v1v2.c directly, no need to check them in
> connect_fd_to_addr() in network_helpers.c.
>
> This also makes connect_fd_to_addr() function useless. It can be replaced
> by connect().
>
> Suggested-by: Martin KaFai Lau <martin.lau@kernel.org>
> Signed-off-by: Geliang Tang <tanggeliang@kylinos.cn>
> ---
> tools/testing/selftests/bpf/network_helpers.c | 31 ++-----------------
> tools/testing/selftests/bpf/network_helpers.h | 1 -
> .../selftests/bpf/prog_tests/cgroup_v1v2.c | 10 ++----
> 3 files changed, 5 insertions(+), 37 deletions(-)
>
> diff --git a/tools/testing/selftests/bpf/network_helpers.c b/tools/testing/selftests/bpf/network_helpers.c
> index 15e0e0bb7553..48c27c810db7 100644
> --- a/tools/testing/selftests/bpf/network_helpers.c
> +++ b/tools/testing/selftests/bpf/network_helpers.c
> @@ -277,33 +277,6 @@ int client_socket(int family, int type,
> return -1;
> }
>
> -static int connect_fd_to_addr(int fd,
> - const struct sockaddr_storage *addr,
> - socklen_t addrlen, const bool must_fail)
> -{
> - int ret;
> -
> - errno = 0;
> - ret = connect(fd, (const struct sockaddr *)addr, addrlen);
> - if (must_fail) {
> - if (!ret) {
> - log_err("Unexpected success to connect to server");
> - return -1;
> - }
> - if (errno != EPERM) {
> - log_err("Unexpected error from connect to server");
> - return -1;
> - }
> - } else {
> - if (ret) {
> - log_err("Failed to connect to server");
> - return -1;
> - }
> - }
> -
> - return 0;
> -}
> -
> int connect_to_addr(int type, const struct sockaddr_storage *addr, socklen_t addrlen,
> const struct network_helper_opts *opts)
> {
> @@ -318,7 +291,7 @@ int connect_to_addr(int type, const struct sockaddr_storage *addr, socklen_t add
> return -1;
> }
>
> - if (connect_fd_to_addr(fd, addr, addrlen, opts->must_fail))
> + if (connect(fd, (const struct sockaddr *)addr, addrlen))
> goto error_close;
>
> return fd;
> @@ -383,7 +356,7 @@ int connect_fd_to_fd(int client_fd, int server_fd, int timeout_ms)
> return -1;
> }
>
> - if (connect_fd_to_addr(client_fd, &addr, len, false))
> + if (connect(client_fd, (const struct sockaddr *)&addr, len))
> return -1;
>
> return 0;
> diff --git a/tools/testing/selftests/bpf/network_helpers.h b/tools/testing/selftests/bpf/network_helpers.h
> index 5b548c0c60de..f39eeb5a4594 100644
> --- a/tools/testing/selftests/bpf/network_helpers.h
> +++ b/tools/testing/selftests/bpf/network_helpers.h
> @@ -23,7 +23,6 @@ typedef __u16 __sum16;
>
> struct network_helper_opts {
> int timeout_ms;
> - bool must_fail;
> int proto;
> /* +ve: Passed to listen() as-is.
> * 0: Default when the test does not set
> diff --git a/tools/testing/selftests/bpf/prog_tests/cgroup_v1v2.c b/tools/testing/selftests/bpf/prog_tests/cgroup_v1v2.c
> index addf720428f7..04e82a486102 100644
> --- a/tools/testing/selftests/bpf/prog_tests/cgroup_v1v2.c
> +++ b/tools/testing/selftests/bpf/prog_tests/cgroup_v1v2.c
> @@ -9,9 +9,6 @@
>
> static int run_test(int cgroup_fd, int server_fd, bool classid)
> {
> - struct network_helper_opts opts = {
> - .must_fail = true,
> - };
> struct connect4_dropper *skel;
> int fd, err = 0;
>
> @@ -32,11 +29,10 @@ static int run_test(int cgroup_fd, int server_fd, bool classid)
> goto out;
> }
>
> - fd = connect_to_fd_opts(server_fd, &opts);
> - if (fd < 0)
> - err = -1;
> - else
> + fd = connect_to_fd_opts(server_fd, NULL);
> + if (fd >= 0)
> close(fd);
> + err = errno != EPERM ? -1 : 0;
Still not right. Can errno be used when fd >= 0? That makes the fd >= 0 case
flaky. fd >= 0 should always be treated as error here (i.e. err = -1). just
always set err = -1 in the fd >= 0 case. No need to be smart here to save a few
lines.
Please take time to review the patches before posting to the list.
pw-bot: cr
next prev parent reply other threads:[~2024-07-12 17:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-12 7:04 [PATCH bpf-next v2 0/5] use network helpers, part 9 Geliang Tang
2024-07-12 7:04 ` [PATCH bpf-next v2 1/5] selftests/bpf: Drop type of connect_to_fd_opts Geliang Tang
2024-07-12 7:04 ` [PATCH bpf-next v2 2/5] selftests/bpf: Drop must_fail from network_helper_opts Geliang Tang
2024-07-12 17:36 ` Martin KaFai Lau [this message]
2024-07-12 7:04 ` [PATCH bpf-next v2 3/5] selftests/bpf: Add connect_to_addr_str helper Geliang Tang
2024-07-12 7:04 ` [PATCH bpf-next v2 4/5] selftests/bpf: Use connect_to_addr_str in sk_lookup Geliang Tang
2024-07-12 7:04 ` [PATCH bpf-next v2 5/5] selftests/bpf: Drop make_socket " Geliang Tang
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=2cf71a18-b2f2-477b-85fb-25a907b8dd73@linux.dev \
--to=martin.lau@linux.dev \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=geliang@kernel.org \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=martin.lau@kernel.org \
--cc=mykolal@fb.com \
--cc=shuah@kernel.org \
--cc=song@kernel.org \
--cc=tanggeliang@kylinos.cn \
--cc=yonghong.song@linux.dev \
/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