From: Daan De Meyer <daan.j.demeyer@gmail.com>
To: bpf@vger.kernel.org
Cc: Daan De Meyer <daan.j.demeyer@gmail.com>,
martin.lau@linux.dev, kernel-team@meta.com,
netdev@vger.kernel.org
Subject: [PATCH bpf-next v6 1/9] selftests/bpf: Add missing section name tests for getpeername/getsockname
Date: Tue, 26 Sep 2023 22:27:40 +0200 [thread overview]
Message-ID: <20230926202753.1482200-2-daan.j.demeyer@gmail.com> (raw)
In-Reply-To: <20230926202753.1482200-1-daan.j.demeyer@gmail.com>
These were missed when these hooks were first added so add them now
instead to make sure every sockaddr hook has a matching section name
test.
Signed-off-by: Daan De Meyer <daan.j.demeyer@gmail.com>
---
.../selftests/bpf/prog_tests/section_names.c | 20 +++++++++++++++++++
1 file changed, 20 insertions(+)
diff --git a/tools/testing/selftests/bpf/prog_tests/section_names.c b/tools/testing/selftests/bpf/prog_tests/section_names.c
index 8b571890c57e..fc5248e94a01 100644
--- a/tools/testing/selftests/bpf/prog_tests/section_names.c
+++ b/tools/testing/selftests/bpf/prog_tests/section_names.c
@@ -158,6 +158,26 @@ static struct sec_name_test tests[] = {
{0, BPF_PROG_TYPE_CGROUP_SOCKOPT, BPF_CGROUP_SETSOCKOPT},
{0, BPF_CGROUP_SETSOCKOPT},
},
+ {
+ "cgroup/getpeername4",
+ {0, BPF_PROG_TYPE_CGROUP_SOCK_ADDR, BPF_CGROUP_INET4_GETPEERNAME},
+ {0, BPF_CGROUP_INET4_GETPEERNAME},
+ },
+ {
+ "cgroup/getpeername6",
+ {0, BPF_PROG_TYPE_CGROUP_SOCK_ADDR, BPF_CGROUP_INET6_GETPEERNAME},
+ {0, BPF_CGROUP_INET6_GETPEERNAME},
+ },
+ {
+ "cgroup/getsockname4",
+ {0, BPF_PROG_TYPE_CGROUP_SOCK_ADDR, BPF_CGROUP_INET4_GETSOCKNAME},
+ {0, BPF_CGROUP_INET4_GETSOCKNAME},
+ },
+ {
+ "cgroup/getsockname6",
+ {0, BPF_PROG_TYPE_CGROUP_SOCK_ADDR, BPF_CGROUP_INET6_GETSOCKNAME},
+ {0, BPF_CGROUP_INET6_GETSOCKNAME},
+ },
};
static void test_prog_type_by_name(const struct sec_name_test *test)
--
2.41.0
next prev parent reply other threads:[~2023-09-26 20:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-26 20:27 [PATCH bpf-next v6 0/9] Add cgroup sockaddr hooks for unix sockets Daan De Meyer
2023-09-26 20:27 ` Daan De Meyer [this message]
2023-09-26 20:27 ` [PATCH bpf-next v6 2/9] bpf: Propagate modified uaddrlen from cgroup sockaddr programs Daan De Meyer
2023-09-27 22:19 ` Martin KaFai Lau
2023-09-26 20:27 ` [PATCH bpf-next v6 3/9] bpf: Add bpf_sock_addr_set_unix_addr() to allow writing unix sockaddr from bpf Daan De Meyer
2023-09-26 20:27 ` [PATCH bpf-next v6 4/9] bpf: Implement cgroup sockaddr hooks for unix sockets Daan De Meyer
2023-09-27 22:32 ` Martin KaFai Lau
2023-09-26 20:27 ` [PATCH bpf-next v6 5/9] libbpf: Add support for cgroup unix socket address hooks Daan De Meyer
2023-09-26 20:27 ` [PATCH bpf-next v6 6/9] bpftool: " Daan De Meyer
2023-09-27 8:26 ` Quentin Monnet
2023-09-26 20:27 ` [PATCH bpf-next v6 7/9] documentation/bpf: Document " Daan De Meyer
2023-09-26 20:27 ` [PATCH bpf-next v6 8/9] selftests/bpf: Make sure mount directory exists Daan De Meyer
2023-09-26 20:27 ` [PATCH bpf-next v6 9/9] selftests/bpf: Add tests for cgroup unix socket address hooks Daan De Meyer
2023-09-27 22:36 ` Martin KaFai Lau
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=20230926202753.1482200-2-daan.j.demeyer@gmail.com \
--to=daan.j.demeyer@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=kernel-team@meta.com \
--cc=martin.lau@linux.dev \
--cc=netdev@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).