selinux_inode_xattr_skipcap(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… selinux_inode_xattr_skipcap β€” like, the Kernel API Manual page, bestie

okay so welcome to the selinux_inode_xattr_skipcap page, part of the Kernel API Manual β€” yes it's a mouthful, no you don't have to say it out loud at parties πŸŽ€


✨ NAME ✨

selinux_inode_xattr_skipcap β€” Skip the xattr capability checks?

Like... should we skip them? That's literally the whole question. Vibe check incoming πŸ’…


🌸 SYNOPSIS 🌸

int selinux_inode_xattr_skipcap (const char *name );

that's it, that's the whole signature, she's lowkey elegant πŸ¦‹


🫢 ARGUMENTS 🫢

  • name β€” name of the xattr. yep. just the name. the name of the xattr. icon behavior honestly πŸ‘‘

πŸ”₯ DESCRIPTION πŸ”₯

okay so here's the tea β˜• β€” this function returns 1 to indicate that SELinux "owns" the access control rights to xattrs named name; the LSM layer should avoid enforcing any traditional capability based access controls on this xattr. no cap, that's what the 1 means 🫑

and it returns 0 to indicate that SELinux does not "own" the access control rights to xattrs named name, and is deferring to the LSM layer for further access controls, including capability based controls. so like, she's handing the aux cord over 🎧

fr fr the return value is the whole point here β€” 1 = SELinux is the main character for this xattr, 0 = SELinux is stepping back and letting the LSM layer run the group chat 😭

🌈 SEE ALSO 🌈

Kernel file ./security/selinux/hooks.c plus this whole friend group:

go read them all, bestie, they're all slay in their own way πŸ’œ


alright that's the page!! source and version moment: this cutie lives under ./security/selinux and it's dated October 2026 β€” mwah, stan her, periodt πŸ’–βœ¨πŸŽ€

πŸ“¦ where this page comes from