vfsgid_in_group_p(9)
π vfsgid_in_group_p(9) β from the Kernel API Manual, bestie β¨
Okay so this one's a little kernel helper, and yes the name is a whole mouthful β it's vfsgid_in_group_p, and the (9) just means it lives in that section of the manual, slay π
πΈ NAME πΈ
vfsgid_in_group_p β check whether a vfsuid matches the caller's groups π
(Yes, the NAME literally says vfsuid even though the function is about gids. That's what the page says, bestie β I'm not out here editing the lore, iykyk π)
β¨ SYNOPSIS β¨
int vfsgid_in_group_p (vfsgid_t vfsgid );
That's it. One argument, one int back. Clean. Minimalist. Main character energy π
π¦ ARGUMENTS π¦
vfsgidβ the mnt gid to match π like, that's the thing you're handing over to get checked.
π DESCRIPTION π
So the way this works: this function can be used to determine whether vfsuid matches any of the caller's groups. That's the whole vibe check β you pass in your mnt gid, it goes and looks at the caller's groups, and tells you if there's a match π
(And yeah, the description says vfsuid β same energy as the NAME. Keeping it exactly as the page wrote it, fr fr π«Ά)
π₯ RETURN π₯
1β yay,vfsuidmatches the caller's groups β0β nope, no match π
Literally a yes-or-no, no in-between, periodt.
π SEE ALSO π
Kernel file ./fs/mnt_idmapping.c, plus the whole friend group:
initial_idmapping(9)make_vfsuid(9)make_vfsgid(9)from_vfsuid(9)from_vfsgid(9)mnt_idmap_get(9)mnt_idmap_put(9)
Go read those too, they're all lowkey iconic π
Heads up bestie: the original page mixesvfsuidandvfsgidin the NAME, DESCRIPTION, and RETURN sections. I kept every word of it the way it was written β no cap, no fixing π
And that's the whole page! π§ Signing off from ./fs, dated October 2026, on the vfsgid_in_group_p(9) page itself β stay hydrated, read your kernel headers, and 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