From: John Fastabend <john.fastabend@gmail.com>
To: Michal Luczaj <mhal@rbox.co>
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>,
Martin KaFai Lau <martin.lau@linux.dev>,
Song Liu <song@kernel.org>,
Yonghong Song <yonghong.song@linux.dev>,
KP Singh <kpsingh@kernel.org>,
Stanislav Fomichev <sdf@fomichev.me>, Hao Luo <haoluo@google.com>,
Jiri Olsa <jolsa@kernel.org>, Shuah Khan <shuah@kernel.org>,
bpf@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org,
Jakub Sitnicki <jakub@cloudflare.com>,
Jiayuan Chen <mrpre@163.com>
Subject: Re: [PATCH bpf-next v3 4/8] selftests/bpf: Introduce verdict programs for sockmap_redir
Date: Wed, 14 May 2025 21:29:16 -0700 [thread overview]
Message-ID: <20250515042900.5dox2mozx455tekm@gmail.com> (raw)
In-Reply-To: <20250515-selftests-sockmap-redir-v3-4-a1ea723f7e7e@rbox.co>
On 2025-05-15 00:15:27, Michal Luczaj wrote:
> Instead of piggybacking on test_sockmap_listen, introduce
> test_sockmap_redir especially for sockmap redirection tests.
>
> Suggested-by: Jiayuan Chen <mrpre@163.com>
> Acked-by: John Fastabend <john.fastabend@gmail.com>
> Signed-off-by: Michal Luczaj <mhal@rbox.co>
> ---
LGTM, this is a net new patch in v3 though correct? In the future
only carry the Acks into patches that are from the previous version
and not substantially changed.
All the same thanks for doing this. For this patch.
Acked-by: John Fastabend <john.fastabend@gmail.com>
next prev parent reply other threads:[~2025-05-15 4:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-14 22:15 [PATCH bpf-next v3 0/8] selftests/bpf: Test sockmap/sockhash redirection Michal Luczaj
2025-05-14 22:15 ` [PATCH bpf-next v3 1/8] selftests/bpf: Support af_unix SOCK_DGRAM socket pair creation Michal Luczaj
2025-05-14 22:15 ` [PATCH bpf-next v3 2/8] selftests/bpf: Add socket_kind_to_str() to socket_helpers Michal Luczaj
2025-05-14 22:15 ` [PATCH bpf-next v3 3/8] selftests/bpf: Add u32()/u64() to sockmap_helpers Michal Luczaj
2025-05-14 22:15 ` [PATCH bpf-next v3 4/8] selftests/bpf: Introduce verdict programs for sockmap_redir Michal Luczaj
2025-05-15 4:29 ` John Fastabend [this message]
2025-05-15 10:49 ` Michal Luczaj
2025-05-14 22:15 ` [PATCH bpf-next v3 5/8] selftests/bpf: Add selftest for sockmap/hashmap redirection Michal Luczaj
2025-05-14 22:15 ` [PATCH bpf-next v3 6/8] selftests/bpf: sockmap_listen cleanup: Drop af_vsock redir tests Michal Luczaj
2025-05-14 22:15 ` [PATCH bpf-next v3 7/8] selftests/bpf: sockmap_listen cleanup: Drop af_unix " Michal Luczaj
2025-05-14 22:15 ` [PATCH bpf-next v3 8/8] selftests/bpf: sockmap_listen cleanup: Drop af_inet SOCK_DGRAM " Michal Luczaj
2025-05-22 22:20 ` [PATCH bpf-next v3 0/8] selftests/bpf: Test sockmap/sockhash redirection patchwork-bot+netdevbpf
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=20250515042900.5dox2mozx455tekm@gmail.com \
--to=john.fastabend@gmail.com \
--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=jakub@cloudflare.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=mhal@rbox.co \
--cc=mrpre@163.com \
--cc=mykolal@fb.com \
--cc=sdf@fomichev.me \
--cc=shuah@kernel.org \
--cc=song@kernel.org \
--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
all inboxes | Powered by JetHome®