From: Leon Hwang <leon.hwang@linux.dev>
To: bpf@vger.kernel.org
Cc: Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
John Fastabend <john.fastabend@gmail.com>,
Andrii Nakryiko <andrii@kernel.org>,
Eduard Zingerman <eddyz87@gmail.com>,
Kumar Kartikeya Dwivedi <memxor@gmail.com>,
Martin KaFai Lau <martin.lau@linux.dev>,
Song Liu <song@kernel.org>,
Yonghong Song <yonghong.song@linux.dev>,
Jiri Olsa <jolsa@kernel.org>,
Emil Tsalapatis <emil@etsalapatis.com>,
Ihor Solodrai <ihor.solodrai@linux.dev>,
Quentin Monnet <qmo@kernel.org>, Shuah Khan <shuah@kernel.org>,
Leon Hwang <leon.hwang@linux.dev>,
Mykyta Yatsenko <yatsenko@meta.com>,
Avinash Duduskar <avinash.duduskar@gmail.com>,
Anton Protopopov <a.s.protopopov@gmail.com>,
Amery Hung <ameryhung@gmail.com>, Jordan Rife <jordan@jrife.io>,
Rong Tao <rongtao@cestc.cn>, Eyal Birger <eyal.birger@gmail.com>,
Pu Lehui <pulehui@huawei.com>,
Jingguo Tan <tanjingguo@huawei.com>, Lin Ma <malin89@huawei.com>,
linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org
Subject: [PATCH bpf-next 09/13] selftests/bpf: Add tracing_multi bpf prog attach failure tests
Date: Sun, 9 Aug 2026 23:01:07 +0800 [thread overview]
Message-ID: <20260809150111.45000-10-leon.hwang@linux.dev> (raw)
In-Reply-To: <20260809150111.45000-1-leon.hwang@linux.dev>
Tests against two libbpf failures and two kernel failures:
* libbpf: 'ids' + 'fds'.
* libbpf: 'pattern' + 'fds'.
* kernel: 'fds' + invalid 'ids'.
* kernel: duplicate targets via different fd for the same bpf prog + func.
Assisted-by: Codex:gpt-5.5
Signed-off-by: Leon Hwang <leon.hwang@linux.dev>
---
.../selftests/bpf/prog_tests/tracing_multi.c | 100 ++++++++++++++++++
1 file changed, 100 insertions(+)
diff --git a/tools/testing/selftests/bpf/prog_tests/tracing_multi.c b/tools/testing/selftests/bpf/prog_tests/tracing_multi.c
index 5ecb751af9be..5cf11707eaf8 100644
--- a/tools/testing/selftests/bpf/prog_tests/tracing_multi.c
+++ b/tools/testing/selftests/bpf/prog_tests/tracing_multi.c
@@ -730,6 +730,104 @@ static void test_attach_api_fails(void)
free(ids2);
}
+static void test_attach_api_bpf_prog_fails(void)
+{
+ static const char * const kfuncs[] = {
+ "bpf_fentry_test1",
+ };
+ const char *bpf_funcs[] = { "target_1" };
+ LIBBPF_OPTS(bpf_tracing_multi_opts, opts);
+ LIBBPF_OPTS(bpf_link_create_opts, lopts);
+ struct tracing_multi_bpf *skel = NULL;
+ int fd, target_id, token_fd;
+ int fds[2], dup_fd = -1;
+ struct bpf_link *link;
+ __u32 target_ids[2];
+ __u32 *ids = NULL;
+ long err;
+
+ skel = tracing_multi_bpf__open_and_load();
+ if (!ASSERT_OK_PTR(skel, "tracing_multi_bpf__open_and_load"))
+ return;
+
+ ids = get_ids(kfuncs, ARRAY_SIZE(kfuncs), NULL);
+ if (!ASSERT_OK_PTR(ids, "get_ids"))
+ goto cleanup;
+
+ fds[0] = bpf_program__fd(skel->progs.target_1);
+
+ /* fail#1 (libbpf) kernel ids and BPF prog fds */
+ LIBBPF_OPTS_RESET(opts,
+ .ids = ids,
+ .fds = fds,
+ .funcs = bpf_funcs,
+ .cnt = ARRAY_SIZE(bpf_funcs),
+ );
+
+ link = bpf_program__attach_tracing_multi(skel->progs.test_fentry, NULL, &opts);
+ err = libbpf_get_error(link);
+ if (!ASSERT_EQ(err, -EINVAL, "libbpf_ids_fds")) {
+ if (!err)
+ bpf_link__destroy(link);
+ goto cleanup;
+ }
+
+ /* fail#2 (libbpf) kernel pattern and BPF prog fds */
+ LIBBPF_OPTS_RESET(opts,
+ .fds = fds,
+ .funcs = bpf_funcs,
+ .cnt = ARRAY_SIZE(bpf_funcs),
+ );
+
+ link = bpf_program__attach_tracing_multi(skel->progs.test_fentry,
+ "bpf_fentry_test*", &opts);
+ err = libbpf_get_error(link);
+ if (!ASSERT_EQ(err, -EINVAL, "libbpf_pattern_fds")) {
+ if (!err)
+ bpf_link__destroy(link);
+ goto cleanup;
+ }
+
+ /* fail#3 (kernel) kernel id with BPF prog fd */
+ lopts.tracing_multi.ids = ids;
+ lopts.tracing_multi.fds = fds;
+ lopts.tracing_multi.cnt = ARRAY_SIZE(bpf_funcs);
+ fd = bpf_link_create(bpf_program__fd(skel->progs.test_fentry), 0,
+ BPF_TRACE_FENTRY_MULTI, &lopts);
+ ASSERT_EQ(fd, -EINVAL, "kernel_id_bpf_fd");
+ if (fd >= 0)
+ close(fd);
+
+ /* fail#4 (kernel) duplicate target through different fds */
+ token_fd = bpf_object__token_fd(skel->obj);
+ token_fd = token_fd < 0 ? 0 : token_fd;
+ target_id = libbpf_find_prog_btf_id("target_1", fds[0], token_fd);
+ if (!ASSERT_GT(target_id, 0, "target_1_btf_id"))
+ goto cleanup;
+
+ dup_fd = dup(fds[0]);
+ if (!ASSERT_GE(dup_fd, 0, "dup_target_fd"))
+ goto cleanup;
+
+ fds[1] = dup_fd;
+ target_ids[0] = target_id;
+ target_ids[1] = target_id;
+ lopts.tracing_multi.ids = target_ids;
+ lopts.tracing_multi.fds = fds;
+ lopts.tracing_multi.cnt = ARRAY_SIZE(fds);
+ fd = bpf_link_create(bpf_program__fd(skel->progs.test_fentry), 0,
+ BPF_TRACE_FENTRY_MULTI, &lopts);
+ ASSERT_EQ(fd, -EINVAL, "duplicate_bpf_target");
+ if (fd >= 0)
+ close(fd);
+
+cleanup:
+ if (dup_fd >= 0)
+ close(dup_fd);
+ tracing_multi_bpf__destroy(skel);
+ free(ids);
+}
+
void serial_test_tracing_multi_bench_attach(void)
{
LIBBPF_OPTS(bpf_tracing_multi_opts, opts);
@@ -1096,4 +1194,6 @@ void test_tracing_multi_test(void)
test_fentry_after_multi();
if (test__start_subtest("link_api_bpf_prog"))
test_link_api_bpf_prog();
+ if (test__start_subtest("attach_api_bpf_prog_fails"))
+ test_attach_api_bpf_prog_fails();
}
--
2.55.0
next prev parent reply other threads:[~2026-08-09 15:03 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-09 15:00 [PATCH bpf-next 00/13] bpf: Add tracing_multi link support for bpf progs Leon Hwang
2026-08-09 15:00 ` [PATCH bpf-next 01/13] bpf: Initialize ftrace_managed in bpf_trampoline_get Leon Hwang
2026-08-09 15:01 ` [PATCH bpf-next 02/13] bpf: Factor out update_fentry_multi helper Leon Hwang
2026-08-09 15:01 ` [PATCH bpf-next 03/13] bpf: Drop unnecessary ftrace_location() in update_fentry_multi() Leon Hwang
2026-08-09 15:01 ` [PATCH bpf-next 04/13] bpf: Add tracing_multi link support for bpf progs Leon Hwang
2026-08-10 13:13 ` Jiri Olsa
2026-08-11 6:12 ` Leon Hwang
2026-08-09 15:01 ` [PATCH bpf-next 05/13] libbpf: " Leon Hwang
2026-08-09 15:01 ` [PATCH bpf-next 06/13] bpf: Add tracing_multi link fdinfo " Leon Hwang
2026-08-09 16:20 ` bot+bpf-ci
2026-08-09 15:01 ` [PATCH bpf-next 07/13] bpf: Add tracing_multi link info " Leon Hwang
2026-08-09 15:01 ` [PATCH bpf-next 08/13] selftests/bpf: Add tracing_multi bpf prog attach test Leon Hwang
2026-08-09 15:01 ` Leon Hwang [this message]
2026-08-09 15:01 ` [PATCH bpf-next 10/13] selftests/bpf: Add tracing_multi bpf prog cookie test Leon Hwang
2026-08-09 16:20 ` bot+bpf-ci
2026-08-09 15:01 ` [PATCH bpf-next 11/13] selftests/bpf: Add tracing_multi bpf prog rollback test Leon Hwang
2026-08-09 15:01 ` [PATCH bpf-next 12/13] selftests/bpf: Add tracing_multi bpf prog link info test Leon Hwang
2026-08-09 15:01 ` [PATCH bpf-next 13/13] selftests/bpf: Test tailcall with fentry.multi Leon Hwang
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=20260809150111.45000-10-leon.hwang@linux.dev \
--to=leon.hwang@linux.dev \
--cc=a.s.protopopov@gmail.com \
--cc=ameryhung@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=avinash.duduskar@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=emil@etsalapatis.com \
--cc=eyal.birger@gmail.com \
--cc=ihor.solodrai@linux.dev \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=jordan@jrife.io \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=malin89@huawei.com \
--cc=martin.lau@linux.dev \
--cc=memxor@gmail.com \
--cc=pulehui@huawei.com \
--cc=qmo@kernel.org \
--cc=rongtao@cestc.cn \
--cc=shuah@kernel.org \
--cc=song@kernel.org \
--cc=tanjingguo@huawei.com \
--cc=yatsenko@meta.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