From: Geliang Tang <geliang@kernel.org>
To: 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>,
Martin KaFai Lau <martin.lau@linux.dev>,
Song Liu <song@kernel.org>,
Yonghong Song <yonghong.song@linux.dev>,
John Fastabend <john.fastabend@gmail.com>,
KP Singh <kpsingh@kernel.org>,
Stanislav Fomichev <sdf@google.com>, Hao Luo <haoluo@google.com>,
Jiri Olsa <jolsa@kernel.org>, Shuah Khan <shuah@kernel.org>
Cc: Geliang Tang <tanggeliang@kylinos.cn>,
bpf@vger.kernel.org, linux-kselftest@vger.kernel.org
Subject: Re: [PATCH bpf-next 0/5] use network helpers, part 2
Date: Tue, 23 Apr 2024 18:37:46 +0800 [thread overview]
Message-ID: <3e6f78988d04ea753ea3adee56863729379adc7f.camel@kernel.org> (raw)
In-Reply-To: <cover.1713613543.git.tanggeliang@kylinos.cn>
Superseded.
v2 has just been sent out.
Thanks,
-Geliang
On Sat, 2024-04-20 at 19:55 +0800, Geliang Tang wrote:
> From: Geliang Tang <tanggeliang@kylinos.cn>
>
> This patchset uses more network helpers in test_sock_addr.c, but
> first of all, patch 2 is needed to make network_helpers.c independent
> of test_progs.c. Then network_helpers.h can be included into
> test_sock_addr.c without compile errors.
>
> Patch 1 and patch 2 address Martin's comments for the previous series
> too.
>
> Geliang Tang (5):
> selftests/bpf: Fix a fd leak in error paths in open_netns
> selftests/bpf: Use log_err in open_netns/close_netns
> selftests/bpf: Use start_server_addr in test_sock_addr
> selftests/bpf: Use connect_to_addr in test_sock_addr
> selftests/bpf: Use make_sockaddr in test_sock_addr
>
> tools/testing/selftests/bpf/Makefile | 3 +-
> tools/testing/selftests/bpf/network_helpers.c | 20 ++-
> tools/testing/selftests/bpf/network_helpers.h | 1 +
> .../selftests/bpf/prog_tests/empty_skb.c | 2 +
> .../bpf/prog_tests/ip_check_defrag.c | 2 +
> .../selftests/bpf/prog_tests/tc_redirect.c | 2 +-
> .../selftests/bpf/prog_tests/test_tunnel.c | 4 +
> .../selftests/bpf/prog_tests/xdp_metadata.c | 16 +++
> tools/testing/selftests/bpf/test_sock_addr.c | 136 +++-------------
> --
> 9 files changed, 61 insertions(+), 125 deletions(-)
>
prev parent reply other threads:[~2024-04-23 10:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-20 11:55 [PATCH bpf-next 0/5] use network helpers, part 2 Geliang Tang
2024-04-20 11:55 ` [PATCH bpf-next 1/5] selftests/bpf: Fix a fd leak in error paths in open_netns Geliang Tang
2024-04-20 11:55 ` [PATCH bpf-next 2/5] selftests/bpf: Use log_err in open_netns/close_netns Geliang Tang
2024-04-20 11:55 ` [PATCH bpf-next 3/5] selftests/bpf: Use start_server_addr in test_sock_addr Geliang Tang
2024-04-20 11:55 ` [PATCH bpf-next 4/5] selftests/bpf: Use connect_to_addr " Geliang Tang
2024-04-20 11:55 ` [PATCH bpf-next 5/5] selftests/bpf: Use make_sockaddr " Geliang Tang
2024-04-23 10:37 ` Geliang Tang [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 \
--in-reply-to=3e6f78988d04ea753ea3adee56863729379adc7f.camel@kernel.org \
--to=geliang@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--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@linux.dev \
--cc=mykolal@fb.com \
--cc=sdf@google.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