Re: [f2fs-dev] [PATCH] f2fs: use the mount idmap for the owner check in f2fs_xattr_advise_set()
| Newsgroups | org.kernel.vger.stable,net.sourceforge.lists.linux-f2fs-devel,org.kernel.vger.linux-kernel |
|---|---|
| Message-ID | <178596484038.530543.7575324835869629902.git-patchwork-notify@kernel.org> |
Hello: This patch was applied to jaegeuk/f2fs.git (dev) by Jaegeuk Kim <[email protected]>: On Thu, 16 Jul 2026 10:59:08 +0800 you wrote: > f2fs_xattr_advise_set() calls inode_owner_or_capable() with &nop_mnt_idmap > before allowing the "system.advise" xattr to be set, instead of the idmap > that the VFS passes to the ->set() handler. > > f2fs supports idmapped mounts, so on such a mount this checks the caller's > fsuid against the unmapped on-disk owner rather than the mapped owner: the > actual owner can be wrongly denied with -EPERM and an unrelated caller > wrongly allowed. Pass the handler's idmap instead. > > [...] Here is the summary with links: - [f2fs-dev] f2fs: use the mount idmap for the owner check in f2fs_xattr_advise_set() https://git.kernel.org/jaegeuk/f2fs/c/a54ffce4637a You are awesome, thank you! -- Deet-doot-dot, I am a bot. https://korg.docs.kernel.org/patchwork/pwbot.html