From: sashiko-bot@kernel.org
To: "Fuyu Zhao" <zhaofuyu@vivo.com>
Cc: bpf@vger.kernel.org
Subject: Re: [RFC PATCH bpf-next v3 2/2] selftests/bpf: add tests for selective kmod BTF loading
Date: Wed, 19 Aug 2026 09:12:24 +0000 [thread overview]
Message-ID: <20260819091224.ED5CB1F00A3D@smtp.kernel.org> (raw)
In-Reply-To: <20260819090426.267-3-zhaofuyu@vivo.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] The custom libbpf print callback silently drops all non-matching libbpf logs, hiding crucial diagnostic information if the test fails.
--
--- Patch [2]: [RFC PATCH bpf-next v3 2/2] selftests/bpf: add tests for selective kmod BTF loading ---
commit 17f3a2340dd7be0947e3baabf30a8c7722ec91fe
Author: Fuyu Zhao <zhaofuyu@vivo.com>
selftests/bpf: add tests for selective kmod BTF loading
This commit adds tests for the selective kmod BTF loading feature. It
covers scenarios such as valid modules, non-existent modules, duplicate
names, unneeded modules, and missing count properties.
> diff --git a/tools/testing/selftests/bpf/prog_tests/kmod_btfs.c b/tools/testing/selftests/bpf/prog_tests/kmod_btfs.c
> new file mode 100644
> index 0000000000000..61d2845a731ff
> --- /dev/null
> +++ b/tools/testing/selftests/bpf/prog_tests/kmod_btfs.c
> @@ -0,0 +1,196 @@
> +// SPDX-License-Identifier: GPL-2.0
> +#include <test_progs.h>
> +#include "kmod_btfs.skel.h"
[ ... ]
> +static int libbpf_print_cb(enum libbpf_print_level level, const char *fmt,
> + va_list args)
> +{
> + if (!strcmp(fmt, btf_skip_fmt)) {
> + if (!strcmp(va_arg(args, char *), "bpf_test_no_cfi"))
> + btf_skipped = true;
> + } else if (!strcmp(fmt, dup_ignore_fmt)) {
> + if (!strcmp(va_arg(args, char *), "bpf_testmod"))
> + dup_ignored = true;
> + }
> +
> + return 0;
> +}
[Severity: Medium]
Does this unconditionally swallow all other libbpf debug, info, and error logs?
Since old_print_cb is stored as a local variable in the subtests (like
kmod_btfs_dup and kmod_btfs_skip) rather than globally, this callback has no
way to forward unmatched logs to the original handler. If a BPF program fails
to load during these tests, will the underlying verifier or libbpf errors be
completely hidden, making CI failures harder to debug?
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260819090426.267-1-zhaofuyu@vivo.com?part=2
next prev parent reply other threads:[~2026-08-19 9:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-19 9:04 [RFC PATCH bpf-next v3 0/2] libbpf: Improve BPF load performance by selectively loading kmod BTFs Fuyu Zhao
2026-08-19 9:04 ` [RFC PATCH bpf-next v3 1/2] libbpf: support selective kernel module BTF loading via bpf_object_open_opts Fuyu Zhao
2026-08-19 9:12 ` sashiko-bot
2026-08-19 9:35 ` bot+bpf-ci
2026-08-19 9:04 ` [RFC PATCH bpf-next v3 2/2] selftests/bpf: add tests for selective kmod BTF loading Fuyu Zhao
2026-08-19 9:12 ` sashiko-bot [this message]
2026-08-19 9:50 ` bot+bpf-ci
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=20260819091224.ED5CB1F00A3D@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
--cc=zhaofuyu@vivo.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