evm_inode_post_set_acl(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… evm_inode_post_set_acl(9) β€” from the Kernel API Manual, bestie

okay so picture this: you're deep in the kernel, you just touched some posix acls, and now the EVM vibes are ✨off✨. this little function is the cleanup crew. she's giving "post-game refresh," and honestly? iconic.


🌸 NAME 🌸

evm_inode_post_set_acl β€” the one where we update the EVM extended attribute from posix acls 🫢


✨ SYNOPSIS ✨

void evm_inode_post_set_acl (struct dentry *dentry , const char
       *acl_name , struct posix_acl *kacl );

like yes, she's void, she returns nothing, she does her job and leaves. main character energy fr fr πŸ”₯


πŸŽ€ ARGUMENTS πŸŽ€

  • dentry β€” pointer to the affected dentry. the actual file/dir that's going through it rn, ngl she's the one we care about πŸ’–
  • acl_name β€” name of the posix acl. just so we know which acl we're talking about, yk?
  • kacl β€” pointer to the posix acls. the acl data itself, arriving at the function like "hi bestie i'm here" πŸ¦‹

πŸ’œ DESCRIPTION πŸ’œ

okay so here's the tea: this function updates the security.evm xattr with the EVM HMAC β€” and yes, that HMAC gets re-calculated after setting the posix acls. so basically the acls change, and the crypto fingerprint has to be redone to match. no cap, that's the whole vibe. ✨


πŸ‘‘ SEE ALSO πŸ‘‘

the whole friend group honestly, they all show up together πŸ’€πŸ’–


aaaand that's the page!! brought to you by ./security/integrity/evm, dated October 2026, and yeah β€” she's still evm_inode_post_set_acl(9). slay, bye 🧚⭐

πŸ“¦ where this page comes from