From: "Emil Tsalapatis" <emil@etsalapatis.com>
To: "Christian Brauner" <brauner@kernel.org>, <bpf@vger.kernel.org>
Cc: "Alexander Viro" <viro@zeniv.linux.org.uk>,
"Jan Kara" <jack@suse.cz>, "Amir Goldstein" <amir73il@gmail.com>,
<linux-fsdevel@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] bpf: have bpf_real_data_inode() take a struct file
Date: Tue, 23 Jun 2026 17:31:33 -0400 [thread overview]
Message-ID: <DJGR01P329CF.F5YUUY35XRL3@etsalapatis.com> (raw)
In-Reply-To: <20260623-work-bpf-real_inode-v2-1-8e8b57dd25f7@kernel.org>
On Tue Jun 23, 2026 at 5:32 AM EDT, Christian Brauner wrote:
> bpf_real_data_inode() must be usable from the bprm_check_security,
> mmap_file and file_mprotect hooks for systemd's RestrictFilesystemAccess
> BPF LSM program, so have it take a struct file instead of a dentry.
>
> Amir Goldstein <amir73il@gmail.com> suggests:
>
> While doing so, rename it from bpf_real_inode() to
> bpf_real_data_inode(). For a regular file on a union/overlay
> filesystem it resolves to the underlying inode that hosts the data,
> but for a non-regular file it returns the overlay inode. The new name
> makes the "inode hosting the data" intent explicit and avoids the
> ambiguity of "the real inode backing a file". Document the
> non-regular-file behavior in the kfunc too.
>
> Both the signature change and the rename are safe because the kfunc
> landed this cycle and has no released users.
>
> Fixes: 9af8c8a54f6e ("bpf: add bpf_real_inode() kfunc")
> Signed-off-by: Christian Brauner (Amutable) <brauner@kernel.org>
Reviewed-by: Emil Tsalapatis <emil@etsalapatis.com>
> ---
> Changes in v2:
> - Rename bpf_real_inode() -> bpf_real_data_inode() (Amir); the new name
> makes the "inode hosting the data" intent explicit.
> - Document that the kfunc returns the overlay inode for non-regular files.
> - Link to v1: https://patch.msgid.link/20260622-work-bpf-real_inode-v1-1-4014eb4cbefd@kernel.org
> ---
> fs/bpf_fs_kfuncs.c | 23 ++++++++++++++---------
> 1 file changed, 14 insertions(+), 9 deletions(-)
>
> diff --git a/fs/bpf_fs_kfuncs.c b/fs/bpf_fs_kfuncs.c
> index 768aca2dc0f0..f1863a891db6 100644
> --- a/fs/bpf_fs_kfuncs.c
> +++ b/fs/bpf_fs_kfuncs.c
> @@ -360,18 +360,23 @@ __bpf_kfunc int bpf_cgroup_read_xattr(struct cgroup *cgroup, const char *name__s
> #endif /* CONFIG_CGROUPS */
>
> /**
> - * bpf_real_inode - get the real inode backing a dentry
> - * @dentry: dentry to resolve
> + * bpf_real_data_inode - get the real inode hosting a file's data
> + * @file: file to resolve
> *
> - * If the dentry is on a union/overlay filesystem, return the underlying, real
> - * inode that hosts the data. Otherwise return the inode attached to the
> - * dentry itself.
> + * Resolve @file to the inode that hosts its data. For a regular file on a
> + * union/overlay filesystem this is the underlying (upper or lower) inode that
> + * stores the data, not the overlay inode.
> *
> - * Return: The real inode backing the dentry, or NULL for a negative dentry.
> + * Data resolution only applies to regular files. For a non-regular file (e.g.
> + * a device node, fifo or socket) on a union/overlay filesystem the overlay
> + * inode itself is returned; for any file on a non-union filesystem the inode
> + * attached to @file is returned.
> + *
> + * Return: The inode hosting @file's data, or NULL.
> */
> -__bpf_kfunc struct inode *bpf_real_inode(struct dentry *dentry)
> +__bpf_kfunc struct inode *bpf_real_data_inode(struct file *file)
> {
> - return d_real_inode(dentry);
> + return d_real_inode(file_dentry(file));
> }
>
> __bpf_kfunc_end_defs();
> @@ -384,7 +389,7 @@ BTF_ID_FLAGS(func, bpf_get_dentry_xattr, KF_SLEEPABLE)
> BTF_ID_FLAGS(func, bpf_get_file_xattr, KF_SLEEPABLE)
> BTF_ID_FLAGS(func, bpf_set_dentry_xattr, KF_SLEEPABLE)
> BTF_ID_FLAGS(func, bpf_remove_dentry_xattr, KF_SLEEPABLE)
> -BTF_ID_FLAGS(func, bpf_real_inode, KF_SLEEPABLE | KF_RET_NULL)
> +BTF_ID_FLAGS(func, bpf_real_data_inode, KF_SLEEPABLE | KF_RET_NULL)
> BTF_KFUNCS_END(bpf_fs_kfunc_set_ids)
>
> static int bpf_fs_kfuncs_filter(const struct bpf_prog *prog, u32 kfunc_id)
>
> ---
> base-commit: 5b33fc6492a7b7a62359157db0f92f5b6e9af690
> change-id: 20260622-work-bpf-real_inode-c3202dbaf0ab
prev parent reply other threads:[~2026-06-23 21:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-23 9:32 [PATCH v2] bpf: have bpf_real_data_inode() take a struct file Christian Brauner
2026-06-23 15:26 ` Amir Goldstein
2026-06-23 16:09 ` Christian Brauner
2026-06-23 21:31 ` Emil Tsalapatis [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=DJGR01P329CF.F5YUUY35XRL3@etsalapatis.com \
--to=emil@etsalapatis.com \
--cc=amir73il@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=brauner@kernel.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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