From: Matt Bobrowski <matt@bobrowski.net>
To: Paul Moore <paul@paul-moore.com>
Cc: daan@amutable.com, KP Singh <kpsingh@kernel.org>,
Christian Brauner <brauner@kernel.org>, Jan Kara <jack@suse.cz>,
Alexander Viro <viro@zeniv.linux.org.uk>,
linux-fsdevel@vger.kernel.org,
linux-security-module@vger.kernel.org
Subject: Re: [PATCH v3 2/2] selftests/bpf: verify mount idmaps reach inode hooks
Date: Wed, 9 Sep 2026 09:20:46 +1000 [thread overview]
Message-ID: <aqCYTn8RwpqrPrgO@lima-development> (raw)
In-Reply-To: <CAHC9VhSmpwpvjVPaEKVVA0BnYkn1M+-f4wYDb8uvcL2MQfH9MA@mail.gmail.com>
On Tue, Sep 08, 2026 at 06:22:31PM -0400, Paul Moore wrote:
> On Fri, Sep 4, 2026 at 10:48 AM Daan De Meyer via B4 Relay
> <devnull+daan.amutable.com@kernel.org> wrote:
> >
> > From: Daan De Meyer <daan@amutable.com>
> >
> > Extend the BPF LSM selftest to exercise create, link, symlink, mkdir,
> > mknod, and permission through both the VFS identity idmap and a real
> > idmapped tmpfs mount.
> >
> > Record the idmap observed by each hook and verify that every updated hook
> > receives the mapping used by the VFS operation. This provides regression
> > coverage for passing mount idmaps through inode security hooks.
> >
> > Signed-off-by: Daan De Meyer <daan@amutable.com>
> > ---
> > tools/testing/selftests/bpf/prog_tests/test_lsm.c | 231 ++++++++++++++++++++++
> > tools/testing/selftests/bpf/progs/lsm.c | 79 ++++++++
> > 2 files changed, 310 insertions(+)
>
> Do any of the BPF LSM folks want to review/ACK this patch from Daan?
Sure, will take a look this evening.
next prev parent reply other threads:[~2026-09-08 23:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-04 14:48 [PATCH v3 0/2] lsm: expose mount idmaps to inode hooks Daan De Meyer via B4 Relay
2026-09-04 14:48 ` [PATCH v3 1/2] " Daan De Meyer via B4 Relay
2026-09-08 22:05 ` Paul Moore
2026-09-08 22:27 ` Casey Schaufler
2026-09-09 11:31 ` Daan De Meyer
2026-09-04 14:48 ` [PATCH v3 2/2] selftests/bpf: verify mount idmaps reach " Daan De Meyer via B4 Relay
2026-09-08 22:22 ` Paul Moore
2026-09-08 23:20 ` Matt Bobrowski [this message]
2026-09-08 22:04 ` [PATCH v3 0/2] lsm: expose mount idmaps to " Paul Moore
2026-09-09 11:28 ` 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=aqCYTn8RwpqrPrgO@lima-development \
--to=matt@bobrowski.net \
--cc=brauner@kernel.org \
--cc=daan@amutable.com \
--cc=jack@suse.cz \
--cc=kpsingh@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=paul@paul-moore.com \
--cc=viro@zeniv.linux.org.uk \
/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