From: Qu Wenruo <wqu@suse.com>
To: Tao Cui <cui.tao@linux.dev>, clm@fb.com, dsterba@suse.com
Cc: josef@toxicpanda.com, brauner@kernel.org, sforshee@kernel.org,
linux-btrfs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, Tao Cui <cuitao@kylinos.cn>
Subject: Re: [PATCH] btrfs: use mount idmap for defrag permission check
Date: Thu, 13 Aug 2026 16:04:05 +0930 [thread overview]
Message-ID: <bd66065f-bae5-482a-84d6-a78850c9cebe@suse.com> (raw)
In-Reply-To: <20260813034146.1207640-1-cui.tao@linux.dev>
在 2026/8/13 13:11, Tao Cui 写道:
> From: Tao Cui <cuitao@kylinos.cn>
>
> btrfs_ioctl_defrag() checks MAY_WRITE with nop_mnt_idmap, which skips
> the mount idmap. On an idmapped mount the owner comparison then uses
> the caller's fsuid against the raw on-disk uid, dropping the mapping.
> Every other permission/owner check in btrfs ioctl uses
> file_mnt_idmap(file) (e.g. :1152, :1310, :1946); this one missed it.
>
> Switch to file_mnt_idmap(file). It equals nop_mnt_idmap on a normal
> mount, and the check stays behind !capable(CAP_SYS_ADMIN), so only
> unprivileged callers on idmapped btrfs change. The RO-fd note in the
> comment above is about the file descriptor, not this inode check, and
> is unaffected.
>
> Signed-off-by: Tao Cui <cuitao@kylinos.cn>
Fixes: 4609e1f18e19 ("fs: port ->permission() to pass mnt_idmap")
Otherwise looks good to me.
Reviewed-by: Qu Wenruo <wqu@suse.com>
> ---
> fs/btrfs/ioctl.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/fs/btrfs/ioctl.c b/fs/btrfs/ioctl.c
> index 72bc9d4f7708..607329dedd50 100644
> --- a/fs/btrfs/ioctl.c
> +++ b/fs/btrfs/ioctl.c
> @@ -2458,7 +2458,7 @@ static int btrfs_ioctl_defrag(struct file *file, void __user *argp)
> * running and allows defrag on files open in read-only mode.
> */
> if (!capable(CAP_SYS_ADMIN) &&
> - inode_permission(&nop_mnt_idmap, inode, MAY_WRITE)) {
> + inode_permission(file_mnt_idmap(file), inode, MAY_WRITE)) {
> ret = -EPERM;
> goto out;
> }
next prev parent reply other threads:[~2026-08-13 6:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-13 3:41 [PATCH] btrfs: use mount idmap for defrag permission check Tao Cui
2026-08-13 6:34 ` Qu Wenruo [this message]
2026-08-13 17:11 ` Seth Forshee
2026-08-14 3:29 ` Qu Wenruo
2026-08-14 5:15 ` Tao Cui
2026-08-14 15:25 ` Seth Forshee
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=bd66065f-bae5-482a-84d6-a78850c9cebe@suse.com \
--to=wqu@suse.com \
--cc=brauner@kernel.org \
--cc=clm@fb.com \
--cc=cui.tao@linux.dev \
--cc=cuitao@kylinos.cn \
--cc=dsterba@suse.com \
--cc=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sforshee@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.