From: Christian Brauner <brauner@kernel.org>
To: Daan De Meyer <daan@amutable.com>
Cc: brauner@kernel.org, jack@suse.cz, paul@paul-moore.com,
viro@zeniv.linux.org.uk, linux-security-module@vger.kernel.org,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 0/2] lsm: expose mount idmaps to inode hooks
Date: Tue, 01 Sep 2026 14:28:37 +0200 [thread overview]
Message-ID: <20260901-tastsinn-beiwohnen-planlos-111784e32433@brauner> (raw)
In-Reply-To: <20260824-lsm-mount-idmaps-v1-0-0414a9641c85@amutable.com>
> OverlayFS performs upper-layer operations through inode-based security
> hooks. Those hooks receive the upper inode and dentry, but not the mount
> idmap used by the VFS operation.
>
> The security layer cannot distinguish an identity-mapped upper from an
> idmapped one or make the same ownership decision as the VFS. The VFS
> layer already passes the idmap down into all relevant inode operations
> so this just brings the security hooks to parity.
Yes, I didn't do it initially but this has been on my ToDo for quite a while.
Thanks for doing this.
>
> So pass the mount idmap through the create, link, symlink, mkdir, mknod,
> and permission hooks. Update the in-tree security implementations and
> non-VFS callers accordingly.
>
> systemd has been shipping systemd-nsresourced for quite a while now. It
> relies on inode and path hooks to perform ownership checks using a bpf lsm.
> To make this actually secure we need to be able to calculate the on-disk
> ownership from the idmap.
All looks good to me, but you need to resend with your SoB added.
I think you dropped this because systemd doesn't require it.
Reviewed-by: Christian Brauner (Amutable) <brauner@kernel.org>
--
prev parent reply other threads:[~2026-09-01 12:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-24 13:28 [PATCH 0/2] lsm: expose mount idmaps to inode hooks Daan De Meyer via B4 Relay
2026-08-24 13:28 ` [PATCH 1/2] " Daan De Meyer via B4 Relay
2026-08-24 13:28 ` [PATCH 2/2] selftests/bpf: verify mount idmaps reach " Daan De Meyer via B4 Relay
2026-09-01 12:28 ` Christian Brauner [this message]
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=20260901-tastsinn-beiwohnen-planlos-111784e32433@brauner \
--to=brauner@kernel.org \
--cc=daan@amutable.com \
--cc=jack@suse.cz \
--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