evm_inode_setxattr(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… evm_inode_setxattr ✨

okay so this is a page from the Kernel API Manual, section 9 β€” aka the kernel-internals zone, bestie. it's giving "you're deep in the source tree now" energy 🧚


🌸 NAME 🌸

evm_inode_setxattr β€” the bouncer at the club door of the EVM extended attribute πŸ’… like, it protects it, fr.


πŸŽ€ SYNOPSIS πŸŽ€

int evm_inode_setxattr (struct mnt_idmap *idmap , struct dentry *dentry
, const char *xattr_name , const void *xattr_value , size_t
xattr_value_len , int flags );

πŸ¦‹ ARGUMENTS πŸ¦‹

  • idmap β€” the idmap of the mount, iykyk 🫢
  • dentry β€” a pointer to the dentry that's being affected
  • xattr_name β€” pointer to the name of the extended attribute we're messing with
  • xattr_value β€” pointer to the new value for that extended attribute
  • xattr_value_len β€” pointer to the length of that new extended attribute value
  • flags β€” the flags that get passed on into filesystem operations πŸ”₯

⭐ DESCRIPTION ⭐

so before the kernel even thinks about letting the 'security.evm' protected xattr get updated, it verifies that the existing value is valid. vibe check first, always πŸ’…

and here's the main character energy: only the kernel should have access to the EVM encrypted key that's needed to calculate the HMAC. so userspace is not allowed to write the HMAC value β€” no cap, that door is locked πŸ”’

also, writing 'security.evm' requires CAP_SYS_ADMIN privileges. periodt. πŸ‘‘


πŸ”₯ SEE ALSO πŸ”₯


ok that's the whole page bestie, go read the source if you want the real tea πŸ“

anyway, this little icon comes from ./security/integrity/evm and it's dated October 2026 β€” mwah, love that for us πŸ’–πŸŽ€πŸ¦‹

πŸ“¦ where this page comes from