From: Philo Lu <lulie@linux.alibaba.com>
To: Tiago Lam <tiagolam@cloudflare.com>,
"David S. Miller" <davem@davemloft.net>,
David Ahern <dsahern@kernel.org>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Willem de Bruijn <willemdebruijn.kernel@gmail.com>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii@kernel.org>,
Martin KaFai Lau <martin.lau@linux.dev>,
Eduard Zingerman <eddyz87@gmail.com>, 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@fomichev.me>, Hao Luo <haoluo@google.com>,
Jiri Olsa <jolsa@kernel.org>, Mykola Lysenko <mykolal@fb.com>,
Shuah Khan <shuah@kernel.org>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
bpf@vger.kernel.org, linux-kselftest@vger.kernel.org,
Jakub Sitnicki <jakub@cloudflare.com>,
kernel-team@cloudflare.com
Subject: Re: [RFC PATCH 3/3] bpf: Add sk_lookup test to use ORIGDSTADDR cmsg.
Date: Fri, 13 Sep 2024 20:10:24 +0800 [thread overview]
Message-ID: <8d5469d2-7525-420b-b506-8de2ecf04734@linux.alibaba.com> (raw)
In-Reply-To: <20240913-reverse-sk-lookup-v1-3-e721ea003d4c@cloudflare.com>
Hi Tiago,
On 2024/9/13 17:39, Tiago Lam wrote:
> This patch reuses the framework already in place for sk_lookup, allowing
> it now to send a reply from the server fd directly, instead of having to
> create a socket bound to the original destination address and reply from
> there. It does this by passing the source address and port from where to
> reply from in a IP_ORIGDSTADDR ancilliary message passed in sendmsg.
>
> Signed-off-by: Tiago Lam <tiagolam@cloudflare.com>
> ---
> tools/testing/selftests/bpf/prog_tests/sk_lookup.c | 70 +++++++++++++++-------
> 1 file changed, 48 insertions(+), 22 deletions(-)
>
> diff --git a/tools/testing/selftests/bpf/prog_tests/sk_lookup.c b/tools/testing/selftests/bpf/prog_tests/sk_lookup.c
> index ae87c00867ba..b99aff2e3976 100644
> --- a/tools/testing/selftests/bpf/prog_tests/sk_lookup.c
> +++ b/tools/testing/selftests/bpf/prog_tests/sk_lookup.c
> @@ -75,6 +75,7 @@ struct test {
> struct inet_addr listen_at;
> enum server accept_on;
> bool reuseport_has_conns; /* Add a connected socket to reuseport group */
> + bool dont_bind_reply; /* Don't bind, send direct from server fd. */
> };
>
> struct cb_opts {
> @@ -363,7 +364,7 @@ static void v4_to_v6(struct sockaddr_storage *ss)
> memset(&v6->sin6_addr.s6_addr[0], 0, 10);
> }
>
> -static int udp_recv_send(int server_fd)
> +static int udp_recv_send(int server_fd, bool dont_bind_reply)
> {
> char cmsg_buf[CMSG_SPACE(sizeof(struct sockaddr_storage))];
> struct sockaddr_storage _src_addr = { 0 };
> @@ -415,26 +416,41 @@ static int udp_recv_send(int server_fd)
> v4_to_v6(dst_addr);
> }
>
> - /* Reply from original destination address. */
> - fd = start_server_addr(SOCK_DGRAM, dst_addr, sizeof(*dst_addr), NULL);
> - if (!ASSERT_OK_FD(fd, "start_server_addr")) {
> - log_err("failed to create tx socket");
> - return -1;
> - }
> + if (dont_bind_reply) {
> + /* Reply directly from server fd, specifying the source address and/or
> + * port in struct msghdr.
> + */
> + n = sendmsg(server_fd, &msg, 0);
> + if (CHECK(n <= 0, "sendmsg", "failed\n")) {
> + log_err("failed to send echo reply");
> + return -1;
> + }
> + } else {
> + /* Reply from original destination address. */
> + fd = socket(dst_addr->ss_family, SOCK_DGRAM, 0);
> + if (CHECK(fd < 0, "socket", "failed\n")) {
> + log_err("failed to create tx socket");
> + return -1;
> + }
>
Just curious, why not use start_server_addr() here like before?
> - msg.msg_control = NULL;
> - msg.msg_controllen = 0;
> - n = sendmsg(fd, &msg, 0);
> - if (CHECK(n <= 0, "sendmsg", "failed\n")) {
> - log_err("failed to send echo reply");
> - ret = -1;
> - goto out;
> - }
> + ret = bind(fd, (struct sockaddr *)dst_addr, sizeof(*dst_addr));
> + if (CHECK(ret, "bind", "failed\n")) {
> + log_err("failed to bind tx socket");
> + close(fd);
> + return ret;
> + }
>
> - ret = 0;
> -out:
> - close(fd);
> - return ret;
> + msg.msg_control = NULL;
> + msg.msg_controllen = 0;
> + n = sendmsg(fd, &msg, 0);
> + if (CHECK(n <= 0, "sendmsg", "failed\n")) {
> + log_err("failed to send echo reply");
> + close(fd);
> + return -1;
> + }
> +
> + close(fd);
> + }
nit: "return 0" missed.
> }
>
--
Philo
next prev parent reply other threads:[~2024-09-13 12:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-13 9:39 [RFC PATCH 0/3] Allow sk_lookup UDP return traffic to egress Tiago Lam
2024-09-13 9:39 ` [RFC PATCH 1/3] ipv4: Run a reverse sk_lookup on sendmsg Tiago Lam
2024-09-18 12:45 ` Willem de Bruijn
2024-09-20 16:57 ` Tiago Lam
2024-09-13 9:39 ` [RFC PATCH 2/3] ipv6: " Tiago Lam
2024-09-13 18:24 ` Martin KaFai Lau
2024-09-17 16:15 ` Tiago Lam
2024-09-24 23:58 ` Martin KaFai Lau
2024-10-11 11:21 ` Tiago Lam
2024-09-14 8:59 ` Simon Horman
2024-09-17 16:06 ` Tiago Lam
2024-09-14 11:40 ` Eric Dumazet
2024-09-17 16:03 ` Tiago Lam
2024-09-13 9:39 ` [RFC PATCH 3/3] bpf: Add sk_lookup test to use ORIGDSTADDR cmsg Tiago Lam
2024-09-13 12:10 ` Philo Lu [this message]
2024-09-17 16:00 ` Tiago Lam
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=8d5469d2-7525-420b-b506-8de2ecf04734@linux.alibaba.com \
--to=lulie@linux.alibaba.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=eddyz87@gmail.com \
--cc=edumazet@google.com \
--cc=haoluo@google.com \
--cc=jakub@cloudflare.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kernel-team@cloudflare.com \
--cc=kpsingh@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=mykolal@fb.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sdf@fomichev.me \
--cc=shuah@kernel.org \
--cc=song@kernel.org \
--cc=tiagolam@cloudflare.com \
--cc=willemdebruijn.kernel@gmail.com \
--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