From: Viktor Malik <vmalik@redhat.com>
To: bpf@vger.kernel.org
Cc: Andrii Nakryiko <andrii@kernel.org>,
Eduard Zingerman <eddyz87@gmail.com>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Martin KaFai Lau <martin.lau@linux.dev>,
Song Liu <song@kernel.org>,
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>,
Jiri Olsa <jolsa@kernel.org>, Shuah Khan <shuah@kernel.org>,
Jordan Rome <linux@jordanrome.com>,
Viktor Malik <vmalik@redhat.com>,
Qais Yousef <qyousef@layalina.io>, Hou Tao <houtao1@huawei.com>
Subject: [PATCH bpf-next v2 0/3] Separate tests that need error injection
Date: Tue, 10 Feb 2026 15:14:29 +0100 [thread overview]
Message-ID: <cover.1770732776.git.vmalik@redhat.com> (raw)
Some enterprise kernels (such as RHEL) do not enable error injection via
BPF (CONFIG_FUNCTION_ERROR_INJECTION and CONFIG_BPF_KPROBE_OVERRIDE).
When running test_progs on such kernels, a lot of test cases fail since
they use sleepable fentry or fmod_ret program types which require error
injection to be enabled. While it is possible to skip these via custom
DENYLIST, some test_progs are not properly split into subtests and
therefore must be entirely skipped.
This patch series split such tests into subtests, namely module_attach
and read_vsyscall. In addition, the last patch separates a sleepable
fentry test out of the LSM test suite into a separate test so that it
can be skipped without skipping other LSM tests.
Changes in v2:
- Fix indices in read_vsyscall/copy_from_user subtest (reported by CI)
Viktor Malik (3):
selftests/bpf: Split module_attach into subtests
selftests/bpf: Split read_vsyscall into subtests
selftests/bpf: Split sleepable fentry from LSM test
.../bpf/prog_tests/fentry_sleepable.c | 28 +++
.../selftests/bpf/prog_tests/module_attach.c | 168 +++++++++++++-----
.../selftests/bpf/prog_tests/read_vsyscall.c | 41 ++++-
.../selftests/bpf/prog_tests/test_lsm.c | 8 -
.../selftests/bpf/progs/fentry_sleepable.c | 28 +++
tools/testing/selftests/bpf/progs/lsm.c | 21 ---
.../selftests/bpf/progs/read_vsyscall.c | 18 +-
.../selftests/bpf/progs/test_module_attach.c | 63 +++----
8 files changed, 249 insertions(+), 126 deletions(-)
create mode 100644 tools/testing/selftests/bpf/prog_tests/fentry_sleepable.c
create mode 100644 tools/testing/selftests/bpf/progs/fentry_sleepable.c
--
2.53.0
next reply other threads:[~2026-02-10 14:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-10 14:14 Viktor Malik [this message]
2026-02-10 14:14 ` [PATCH bpf-next v2 1/3] selftests/bpf: Split module_attach into subtests Viktor Malik
2026-02-10 14:47 ` bot+bpf-ci
2026-02-10 16:01 ` Mykyta Yatsenko
2026-02-10 20:45 ` Viktor Malik
2026-02-10 14:14 ` [PATCH bpf-next v2 2/3] selftests/bpf: Split read_vsyscall " Viktor Malik
2026-02-10 14:14 ` [PATCH bpf-next v2 3/3] selftests/bpf: Split sleepable fentry from LSM test Viktor Malik
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=cover.1770732776.git.vmalik@redhat.com \
--to=vmalik@redhat.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=houtao1@huawei.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux@jordanrome.com \
--cc=martin.lau@linux.dev \
--cc=qyousef@layalina.io \
--cc=sdf@fomichev.me \
--cc=shuah@kernel.org \
--cc=song@kernel.org \
--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