From: JP Kobryn <inwardvessel@gmail.com>
To: andrii@kernel.org, ast@kernel.org, eddyz87@gmail.com,
bpf@vger.kernel.org
Subject: [PATCH bpf-next v2 3/3] bpf/selftests: coverage for new program types using cpumask kfuncs
Date: Mon, 26 Aug 2024 15:48:14 -0700 [thread overview]
Message-ID: <20240826224814.289034-4-inwardvessel@gmail.com> (raw)
In-Reply-To: <20240826224814.289034-1-inwardvessel@gmail.com>
This coverage ensures that the cpumask family of kfuncs are allowed within
tracepoint, kprobe, and perf event programs.
Signed-off-by: JP Kobryn <inwardvessel@gmail.com>
---
.../bpf/progs/verifier_kfunc_prog_types.c | 24 +++++++++++++++++++
1 file changed, 24 insertions(+)
diff --git a/tools/testing/selftests/bpf/progs/verifier_kfunc_prog_types.c b/tools/testing/selftests/bpf/progs/verifier_kfunc_prog_types.c
index cb32b0cfc84b..ac1a64974187 100644
--- a/tools/testing/selftests/bpf/progs/verifier_kfunc_prog_types.c
+++ b/tools/testing/selftests/bpf/progs/verifier_kfunc_prog_types.c
@@ -120,3 +120,27 @@ int BPF_PROG(cpumask_kfunc_syscall)
cpumask_kfunc_load_test();
return 0;
}
+
+SEC("tracepoint")
+__success
+int BPF_PROG(cpumask_kfunc_tracepoint)
+{
+ cpumask_kfunc_load_test();
+ return 0;
+}
+
+SEC("kprobe")
+__success
+int BPF_PROG(cpumask_kfunc_kprobe)
+{
+ cpumask_kfunc_load_test();
+ return 0;
+}
+
+SEC("perf_event")
+__success
+int BPF_PROG(cpumask_kfunc_perf_event)
+{
+ cpumask_kfunc_load_test();
+ return 0;
+}
--
2.46.0
prev parent reply other threads:[~2024-08-26 22:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-26 22:48 [PATCH bpf-next v2 0/3] allow cpumask kfuncs in tracepoint, kprobe, perf event JP Kobryn
2024-08-26 22:48 ` [PATCH bpf-next v2 1/3] bpf: new btf kfunc hooks for tracepoint and " JP Kobryn
2024-08-27 21:01 ` Alexei Starovoitov
2024-08-27 22:42 ` Andrii Nakryiko
2024-08-28 19:08 ` JP Kobryn
2024-08-31 2:14 ` Alexei Starovoitov
2024-08-26 22:48 ` [PATCH bpf-next v2 2/3] bpf: register additional prog types with cpumask kfuncs JP Kobryn
2024-08-26 22:48 ` JP Kobryn [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=20240826224814.289034-4-inwardvessel@gmail.com \
--to=inwardvessel@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=eddyz87@gmail.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