From: Martin KaFai Lau <martin.lau@linux.dev>
To: zhangmingyi <zhangmingyi5@huawei.com>
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
song@kernel.org, yhs@fb.com, john.fastabend@gmail.com,
kpsingh@kernel.org, sdf@google.com, haoluo@google.com,
jolsa@kernel.org, bpf@vger.kernel.org,
linux-kernel@vger.kernel.org, yanan@huawei.com,
wuchangye@huawei.com, xiesongyang@huawei.com,
liuxin350@huawei.com, liwei883@huawei.com, tianmuyang@huawei.com
Subject: Re: [PATCH v2 2/2] bpf-next: selftest for TCP_ULP in bpf_setsockopt
Date: Thu, 13 Feb 2025 15:19:20 -0800 [thread overview]
Message-ID: <4533d108-9617-4021-b7a9-befe209926da@linux.dev> (raw)
In-Reply-To: <20250210134550.3189616-3-zhangmingyi5@huawei.com>
On 2/10/25 5:45 AM, zhangmingyi wrote:
> From: Mingyi Zhang <zhangmingyi5@huawei.com>
>
> We try to use bpf_set/getsockopt to set/get TCP_ULP in sockops, and "tls"
> need connect is established.To avoid impacting other test cases, I have
> written a separate test case file.
>
> Signed-off-by: Mingyi Zhang <zhangmingyi5@huawei.com>
> Signed-off-by: Xin Liu <liuxin350@huawei.com>
> ---
> .../bpf/prog_tests/setget_sockopt_tcp_ulp.c | 78 +++++++++++++++++++
> .../bpf/progs/setget_sockopt_tcp_ulp.c | 33 ++++++++
> 2 files changed, 111 insertions(+)
> create mode 100644 tools/testing/selftests/bpf/prog_tests/setget_sockopt_tcp_ulp.c
> create mode 100644 tools/testing/selftests/bpf/progs/setget_sockopt_tcp_ulp.c
>
> diff --git a/tools/testing/selftests/bpf/prog_tests/setget_sockopt_tcp_ulp.c b/tools/testing/selftests/bpf/prog_tests/setget_sockopt_tcp_ulp.c
> new file mode 100644
> index 000000000000..748da2c7d255
> --- /dev/null
> +++ b/tools/testing/selftests/bpf/prog_tests/setget_sockopt_tcp_ulp.c
> @@ -0,0 +1,78 @@
> +// SPDX-License-Identifier: GPL-2.0
> +/* Copyright (c) Meta Platforms, Inc. and affiliates. */
This is not right.
> +
> +#define _GNU_SOURCE
> +#include <net/if.h>
> +
> +#include "test_progs.h"
> +#include "network_helpers.h"
> +
> +#include "setget_sockopt_tcp_ulp.skel.h"
> +
> +#define CG_NAME "/setget-sockopt-tcp-ulp-test"
> +
> +static const char addr4_str[] = "127.0.0.1";
> +static const char addr6_str[] = "::1";
> +static struct setget_sockopt_tcp_ulp *skel;
> +static int cg_fd;
> +
> +static int create_netns(void)
> +{
> + if (!ASSERT_OK(unshare(CLONE_NEWNET), "create netns"))
> + return -1;
> + if (!ASSERT_OK(system("ip link set dev lo up"), "set lo up"))
> + return -1;
> + return 0;
> +}
> +
> +static int modprobe_tls(void)
> +{
> + if (!ASSERT_OK(system("modprobe tls"), "tls modprobe failed"))
> + return -1;
> + return 0;
> +}
> +
> +static void test_tcp_ulp(int family)
First, the bpf CI still fails to compile for the same reason as v1. You should
have received an email from bpf CI bot. Please ensure it is addressed first
before reposting. This repeated bpf CI error is an automatic nack.
pw-bot: cr
The subject tagging should be "[PATCH v2 bpf-next ...] selftests/bpf: ... ".
There are many examples to follow in the mailing list if it is not clear.
Regarding the v1 comment: "...separate it out into its own BPF program..."
The comment was made at the bpf prog file, "progs/setget_sockopt.c". I meant
only create a separate bpf program. The user space part can stay in
prog_tests/setget_sockopt.c.
Move this function, test_tcp_ulp, to prog_tests/setget_sockopt.c. Then all the
above config preparation codes and the test_setget_sockopt_tcp_ulp() can be
saved. modprobe_tls() is not needed also. Do it after the test_ktls().
Take a look at test_nonstandard_opt() in prog_tests/setget_sockopt.c.
It is testing another bpf prog in the same prog_tests/setget_sockopt.c.
Also, for the bpf prog, do you really need to test at
BPF_SOCK_OPS_ACTIVE_ESTABLISHED_CB? If not, just testing at
SEC("lsm_cgroup/socket_post_create") will be easier. You can detach the
previously attached skel->links.socket_post_create by using bpf_link__destroy()
first and then attach yours bpf prog to do the test.
> +{
> + struct setget_sockopt_tcp_ulp__bss *bss = skel->bss;
> + int sfd, cfd;
> +
> + memset(bss, 0, sizeof(*bss));
> + sfd = start_server(family, SOCK_STREAM,
> + family == AF_INET6 ? addr6_str : addr4_str, 0, 0);
> + if (!ASSERT_GE(sfd, 0, "start_server"))
> + return;
> +
> + cfd = connect_to_fd(sfd, 0);
> + if (!ASSERT_GE(cfd, 0, "connect_to_fd_server")) {
> + close(sfd);
> + return;
> + }
> + close(sfd);
> + close(cfd);
> +
> + ASSERT_EQ(bss->nr_tcp_ulp, 3, "nr_tcp_ulp");
> +}
> +
> +void test_setget_sockopt_tcp_ulp(void)
> +{
> + cg_fd = test__join_cgroup(CG_NAME);
> + if (cg_fd < 0)
> + return;
> + if (create_netns() && modprobe_tls())
> + goto done;
> + skel = setget_sockopt_tcp_ulp__open();
> + if (!ASSERT_OK_PTR(skel, "open skel"))
> + goto done;
> + if (!ASSERT_OK(setget_sockopt_tcp_ulp__load(skel), "load skel"))
> + goto done;
> + skel->links.skops_sockopt_tcp_ulp =
> + bpf_program__attach_cgroup(skel->progs.skops_sockopt_tcp_ulp, cg_fd);
> + if (!ASSERT_OK_PTR(skel->links.skops_sockopt_tcp_ulp, "attach_cgroup"))
> + goto done;
> + test_tcp_ulp(AF_INET);
> + test_tcp_ulp(AF_INET6);
> +done:
> + setget_sockopt_tcp_ulp__destroy(skel);
> + close(cg_fd);
> +}
> diff --git a/tools/testing/selftests/bpf/progs/setget_sockopt_tcp_ulp.c b/tools/testing/selftests/bpf/progs/setget_sockopt_tcp_ulp.c
> new file mode 100644
> index 000000000000..bd1009766463
> --- /dev/null
> +++ b/tools/testing/selftests/bpf/progs/setget_sockopt_tcp_ulp.c
> @@ -0,0 +1,33 @@
> +// SPDX-License-Identifier: GPL-2.0
> +/* Copyright (c) Meta Platforms, Inc. and affiliates. */
Same here.
> +
> +#include "vmlinux.h"
> +#include "bpf_tracing_net.h"
> +#include <bpf/bpf_helpers.h>
> +
> +int nr_tcp_ulp;
> +
> +SEC("sockops")
> +int skops_sockopt_tcp_ulp(struct bpf_sock_ops *skops)
> +{
> + static const char target_ulp[] = "tls";
> + char verify_ulp[sizeof(target_ulp)];
> +
> + switch (skops->op) {
> + case BPF_SOCK_OPS_ACTIVE_ESTABLISHED_CB:
> + if (bpf_setsockopt(skops, IPPROTO_TCP, TCP_ULP, (void *)target_ulp,
> + sizeof(target_ulp)) != 0)
> + return 1;
> + nr_tcp_ulp++;
> + if (bpf_getsockopt(skops, IPPROTO_TCP, TCP_ULP, verify_ulp,
> + sizeof(verify_ulp)) != 0)
> + return 1;
> + nr_tcp_ulp++;
> + if (bpf_strncmp(verify_ulp, sizeof(target_ulp), "tls") != 0)
> + return 1;
> + nr_tcp_ulp++;
> + }
> + return 1;
> +}
> +
> +char _license[] SEC("license") = "GPL";
> \ No newline at end of file
next prev parent reply other threads:[~2025-02-13 23:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-10 13:45 [PATCH v2 0/2] bpf-next: Introduced to support the ULP to get or set sockets zhangmingyi
2025-02-10 13:45 ` [PATCH v2 1/2] " zhangmingyi
2025-02-13 23:17 ` Martin KaFai Lau
2025-02-14 2:13 ` kernel test robot
2025-02-14 6:23 ` Martin KaFai Lau
2025-02-14 21:20 ` Jakub Kicinski
2025-02-14 22:11 ` Martin KaFai Lau
2025-02-10 13:45 ` [PATCH v2 2/2] bpf-next: selftest for TCP_ULP in bpf_setsockopt zhangmingyi
2025-02-13 23:19 ` Martin KaFai Lau [this message]
2025-02-28 6:44 ` zhangmingyi
2025-02-14 17:44 ` kernel test robot
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=4533d108-9617-4021-b7a9-befe209926da@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=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liuxin350@huawei.com \
--cc=liwei883@huawei.com \
--cc=sdf@google.com \
--cc=song@kernel.org \
--cc=tianmuyang@huawei.com \
--cc=wuchangye@huawei.com \
--cc=xiesongyang@huawei.com \
--cc=yanan@huawei.com \
--cc=yhs@fb.com \
--cc=zhangmingyi5@huawei.com \
/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