smack_inode_xattr_skipcap(9)

📦 version 7.3.1, in nixpkgs unstable

💅 smack_inode_xattr_skipcap — the kernel API manual, bestie edition 🎀

okay so you're in the 9 section of the kernel API manual and you found smack_inode_xattr_skipcap?? slay, you're literally in the security subsystem now. let me explain the whole vibe ✨

🌸 NAME 🌸

smack_inode_xattr_skipcap — literally asking the question: are we skipping the xattr capability checks or not? 💭

🦋 SYNOPSIS 🦋

int smack_inode_xattr_skipcap (const char *name );

that's it. one function, one argument, one int coming back at you. iconic. 👑

🎀 ARGUMENTS 🎀

  • name — the name of the xattr. that's the whole parameter, bestie, she's simple like that 💖

✨ DESCRIPTION ✨

so here's the tea ☕ — this function is basically the vibe check for who owns the access control rights on a given xattr.

  • Returns 1 to indicate that Smack "owns" the access control rights to xattrs named name; the LSM layer should avoid enforcing any traditional capability based access controls on this xattr. 🫶 like, Smack's got it, everyone else can chill.
  • Returns 0 to indicate that Smack 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. 🙈 handoff moment, she's passing the baton.

no cap, that's the entire contract. 1 = Smack is the main character here, 0 = Smack is like "not my circus, LSM layer, you take this one." 🤷‍♀️

🌈 SEE ALSO 🌈

okay this list is long, and it's genuinely giving "the entire Smack cast list in one place." 💀 They're all referenced from the Kernel file ./security/smack/smack_lsm.c — so if you want the full lore, that's where to go. Get comfy, grab a 🍓, we're going through all of them:

yeah. that's all of them. iykyk 💜

okay bestie, that's the whole page 🫶 — this one came from the Kernel API Manual, lives under ./security/smack, and was dated October 2026. go forth and skip (or not skip) those cap checks with confidence, mwah 💋✨

📦 where this page comes from