From: Christian Brauner <brauner@kernel.org>
To: Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
bpf@vger.kernel.org
Cc: KP Singh <kpsingh@kernel.org>,
Andrii Nakryiko <andrii@kernel.org>,
Martin KaFai Lau <martin.lau@linux.dev>,
linux-kernel@vger.kernel.org,
Christian Brauner <brauner@kernel.org>
Subject: [PATCH 0/2] bpf: classify block device hooks and add selftests
Date: Fri, 20 Feb 2026 18:48:47 +0100 [thread overview]
Message-ID: <20260220-work-bpf-bdev-v1-0-c53e852c4702@kernel.org> (raw)
A bunch of new hooks for managing block devices were added a while ago
but they weren't appropriately classified. Classify them and add a test
program so we catch regressions.
Note that for whatever reason building the bpf selftests locally seems
to fail for all kinds of arcane reasons for me. That might just be my
fault. I added a pr against the ci to have the selftests run but to test
this meaningfully it needs veritysetup and dmverity support. I'm not
sure if that's available already.
Signed-off-by: Christian Brauner <brauner@kernel.org>
---
Christian Brauner (2):
bpf: classify block device hooks appropriately
selftests/bpf: add block device management selftests
kernel/bpf/bpf_lsm.c | 4 +
tools/testing/selftests/bpf/prog_tests/lsm_bdev.c | 221 ++++++++++++++++++++++
tools/testing/selftests/bpf/progs/lsm_bdev.c | 96 ++++++++++
3 files changed, 321 insertions(+)
---
base-commit: 42042907fd759c36922defd1befd318c7467fa1d
change-id: 20260220-work-bpf-bdev-ff2c82143d05
next reply other threads:[~2026-02-20 17:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-20 17:48 Christian Brauner [this message]
2026-02-20 17:48 ` [PATCH 1/2] bpf: classify block device hooks appropriately Christian Brauner
2026-02-20 18:28 ` Christoph Hellwig
2026-02-23 13:42 ` Christian Brauner
2026-02-20 17:48 ` [PATCH 2/2] selftests/bpf: add block device management selftests Christian Brauner
2026-03-23 14:22 ` [PATCH 0/2] bpf: classify block device hooks and add selftests Christian Brauner
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=20260220-work-bpf-bdev-v1-0-c53e852c4702@kernel.org \
--to=brauner@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@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