from_vfsuid(9)
π¦ NAME π¦
from_vfsuid β map a vfsuid into the filesystem idmapping π and yes bestie, this is from_vfsuid(9) from the Kernel API Manual, hi hi π«Ά
β¨ SYNOPSIS β¨
okay so the whole vibe check is literally this:
kuid_t from_vfsuid (struct mnt_idmap *idmap , struct user_namespace
*fs_userns , vfsuid_t vfsuid );
no cap, that's the signature π
π ARGUMENTS π
idmapβ the mount's idmapping πΈfs_usernsβ the filesystem's idmapping π¦vfsuidβ vfsuid to be mapped β¨
π DESCRIPTION π
Map vfsuid into the filesystem idmapping. That's the assignment, periodt. This function has to be used in order to e.g. write vfsuid to inode->i_uid β like, that's the required move, not optional lore ππ₯
π RETURN π
vfsuid mapped into the filesystem idmapping β¨ β that's what comes back to you, bestie π«Ά
π SEE ALSO π
- Kernel file
./fs/mnt_idmapping.cπ initial_idmapping(9)make_vfsuid(9)make_vfsgid(9)from_vfsgid(9)vfsgid_in_group_p(9)mnt_idmap_get(9)mnt_idmap_put(9)
cute sign-off time: this iconic little page comes from source/version ./fs, dated October 2026, and it's still from_vfsuid(9) β mwah ππ
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms