From: Jiri Olsa <olsajiri@gmail.com>
To: Sun Jian <sun.jian.kdev@gmail.com>
Cc: bpf@vger.kernel.org, Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii@kernel.org>,
Shuah Khan <shuah@kernel.org>,
Steven Rostedt <rostedt@goodmis.org>, Song Liu <song@kernel.org>,
Martin KaFai Lau <martin.lau@linux.dev>,
Eduard Zingerman <eddyz87@gmail.com>,
Yonghong Song <yonghong.song@linux.dev>,
John Fastabend <john.fastabend@gmail.com>,
KP Singh <kpsingh@kernel.org>,
Stanislav Fomichev <sdf@fomichev.me>, Hao Luo <haoluo@google.com>,
linux-kselftest@vger.kernel.org
Subject: Re: [PATCH v2 bpf-next] selftests/bpf: livepatch_trampoline: skip when prerequisites are missing
Date: Thu, 5 Mar 2026 10:01:59 +0100 [thread overview]
Message-ID: <aalGh2sjKl_mZp7G@krava> (raw)
In-Reply-To: <20260305030258.5273-1-sun.jian.kdev@gmail.com>
On Thu, Mar 05, 2026 at 11:02:58AM +0800, Sun Jian wrote:
> livepatch_trampoline relies on livepatch sysfs and livepatch-sample.ko.
> When CONFIG_LIVEPATCH is disabled or the samples module isn't built, the
> test fails with ENOENT and causes false failures in minimal CI configs.
>
> Skip the test when livepatch sysfs or the sample module is unavailable.
> Also avoid writing to livepatch sysfs when it's not present.
>
> Signed-off-by: Sun Jian <sun.jian.kdev@gmail.com>
> ---
>
> v2:
> - Add missing Cc's suggested by get_maintainer.pl
> - Prefix subject with bpf-next to avoid Patchwork tree mis-detection
> - Drop Fixes tag to avoid verify_fixes issues due to tree mismatch
> - No code changes
>
> v1: https://patchew.org/linux/20260227042354.20926-1-sun.jian.kdev@gmail.com/
>
> .../bpf/prog_tests/livepatch_trampoline.c | 28 ++++++++++++++++++-
> 1 file changed, 27 insertions(+), 1 deletion(-)
>
> diff --git a/tools/testing/selftests/bpf/prog_tests/livepatch_trampoline.c b/tools/testing/selftests/bpf/prog_tests/livepatch_trampoline.c
> index 72aa5376c30e..75336d9c2313 100644
> --- a/tools/testing/selftests/bpf/prog_tests/livepatch_trampoline.c
> +++ b/tools/testing/selftests/bpf/prog_tests/livepatch_trampoline.c
> @@ -2,9 +2,12 @@
> /* Copyright (c) 2025 Meta Platforms, Inc. and affiliates. */
>
> #include <test_progs.h>
> +#include <unistd.h>
> #include "testing_helpers.h"
> #include "livepatch_trampoline.skel.h"
>
> +#define LIVEPATCH_ENABLED_PATH "/sys/kernel/livepatch/livepatch_sample/enabled"
> +
> static int load_livepatch(void)
> {
> char path[4096];
> @@ -19,7 +22,8 @@ static int load_livepatch(void)
> static void unload_livepatch(void)
> {
> /* Disable the livepatch before unloading the module */
> - system("echo 0 > /sys/kernel/livepatch/livepatch_sample/enabled");
> + if (!access(LIVEPATCH_ENABLED_PATH, F_OK))
> + system("echo 0 > " LIVEPATCH_ENABLED_PATH);
>
> unload_module("livepatch_sample", env_verbosity > VERBOSE_NONE);
> }
> @@ -82,6 +86,28 @@ void test_livepatch_trampoline(void)
> {
> int retry_cnt = 0;
>
> + /* Skip if kernel was built without CONFIG_LIVEPATCH */
> + if (access("/sys/kernel/livepatch", F_OK)) {
> + test__skip();
> + return;
> + }
> +
> + /*
> + * Skip if livepatch-sample.ko was not built (same path logic as
> + * load_livepatch()).
> + */
> + {
> + char path[4096];
> +
> + snprintf(path, sizeof(path),
> + "%s/samples/livepatch/livepatch-sample.ko",
> + getenv("KBUILD_OUTPUT") ? : "../../../..");
> + if (access(path, R_OK)) {
> + test__skip();
> + return;
> + }
> + }
> +
> retry:
> if (load_livepatch()) {
load_livepatch returns -ENOENT if we fail to open the file, we could
check for it instead of putting together the path again
jirka
next prev parent reply other threads:[~2026-03-05 9:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-05 3:02 [PATCH v2 bpf-next] selftests/bpf: livepatch_trampoline: skip when prerequisites are missing Sun Jian
2026-03-05 9:01 ` Jiri Olsa [this message]
2026-03-09 3:50 ` sun jian
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=aalGh2sjKl_mZp7G@krava \
--to=olsajiri@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=kpsingh@kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=rostedt@goodmis.org \
--cc=sdf@fomichev.me \
--cc=shuah@kernel.org \
--cc=song@kernel.org \
--cc=sun.jian.kdev@gmail.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