From: sashiko-bot@kernel.org
To: "Jiri Olsa" <jolsa@kernel.org>
Cc: bpf@vger.kernel.org
Subject: Re: [PATCHv3 bpf-next 6/7] selftests/bpf: Add uprobe_multi path_fd fail tests
Date: Thu, 11 Jun 2026 11:54:31 +0000 [thread overview]
Message-ID: <20260611115432.1FEA01F00893@smtp.kernel.org> (raw)
In-Reply-To: <20260611114230.950379-7-jolsa@kernel.org>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] The patch introduces a compilation failure because it uses the undeclared macro BPF_F_UPROBE_MULTI_PATH_FD and references a non-existent struct member 'path_fd' in struct bpf_link_create_opts.
--
commit acbff7cfc9a00c3bfed7027c436c6abc5a678d5d
Author: Jiri Olsa <jolsa@kernel.org>
selftests/bpf: Add uprobe_multi path_fd fail tests
This commit adds new tests to the attach_api_fails suite in
uprobe_multi_test.c to ensure that incorrect setups using path_fd fail
as expected.
> diff --git a/tools/testing/selftests/bpf/prog_tests/uprobe_multi_test.c b/tools/testing/selftests/bpf/prog_tests/uprobe_multi_test.c
> index 56cbea280fbd2..58a7db7fba902 100644
> --- a/tools/testing/selftests/bpf/prog_tests/uprobe_multi_test.c
> +++ b/tools/testing/selftests/bpf/prog_tests/uprobe_multi_test.c
[ ... ]
> @@ -536,7 +536,37 @@ static void test_attach_api_fails(void)
> link_fd = bpf_link_create(prog_fd, 0, BPF_TRACE_UPROBE_MULTI, &opts);
> if (!ASSERT_ERR(link_fd, "link_fd"))
> goto cleanup;
> - ASSERT_EQ(link_fd, -EINVAL, "pid_is_wrong");
> + if (!ASSERT_EQ(link_fd, -EINVAL, "pid_is_wrong"))
> + goto cleanup;
> +
> + /* wrong path_fd */
> + LIBBPF_OPTS_RESET(opts,
> + .uprobe_multi.path = NULL,
> + .uprobe_multi.path_fd = -1,
> + .uprobe_multi.flags = BPF_F_UPROBE_MULTI_PATH_FD,
[Severity: Low]
Does this cause a compilation failure? The struct member path_fd in
bpf_link_create_opts and the BPF_F_UPROBE_MULTI_PATH_FD macro appear to be
missing or undeclared here, which would typically cause the compiler to fail
with an undeclared identifier error.
> + .uprobe_multi.offsets = (unsigned long *)&offset,
> + .uprobe_multi.cnt = 1,
> + );
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260611114230.950379-7-jolsa@kernel.org?part=1
next prev parent reply other threads:[~2026-06-11 11:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-11 11:42 [PATCHv3 bpf-next 0/7] bpf: Allow uprobe_multi binary specified by file descriptor Jiri Olsa
2026-06-11 11:42 ` [PATCHv3 bpf-next 1/7] bpf: Guard __get_user acesss with access_ok for uprobe_multi data Jiri Olsa
2026-06-11 11:55 ` sashiko-bot
2026-06-11 11:42 ` [PATCHv3 bpf-next 2/7] bpf: Use user_path_at for path resolution in uprobe_multi Jiri Olsa
2026-06-11 11:42 ` [PATCHv3 bpf-next 3/7] bpf: Add support to specify uprobe_multi target via file descriptor Jiri Olsa
2026-06-11 11:42 ` [PATCHv3 bpf-next 4/7] libbpf: Add path_fd to struct bpf_link_create_opts Jiri Olsa
2026-06-11 11:53 ` sashiko-bot
2026-06-11 11:42 ` [PATCHv3 bpf-next 5/7] selftests/bpf: Add uprobe_multi path_fd test Jiri Olsa
2026-06-11 11:52 ` sashiko-bot
2026-06-11 11:42 ` [PATCHv3 bpf-next 6/7] selftests/bpf: Add uprobe_multi path_fd fail tests Jiri Olsa
2026-06-11 11:54 ` sashiko-bot [this message]
2026-06-11 11:42 ` [PATCHv3 bpf-next 7/7] selftests/bpf: Fix typo in verify_umulti_link_info Jiri Olsa
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=20260611115432.1FEA01F00893@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=jolsa@kernel.org \
--cc=sashiko-reviews@lists.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.