evm_inode_post_remove_acl(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– evm_inode_post_remove_acl(9) πŸ’–

okay so bestie, we're in the Kernel API Manual today and this one is literally about keeping your EVM vibes immaculate after somebody rips a POSIX ACL off an inode. it's giving "cleanup crew but make it cryptography" πŸ’…


✨ NAME ✨

evm_inode_post_remove_acl β€” Update the EVM extended attribute from posix acls

like, it refreshes the EVM xattr so it matches reality after a posix acl dips out πŸŽ€


πŸ¦‹ SYNOPSIS πŸ¦‹

void evm_inode_post_remove_acl (struct mnt_idmap *idmap , struct dentry
*dentry , const char *acl_name );

no cap, that's the whole signature. void return, so nothing comes back to you β€” it just does the thing 🫢


🌸 ARGUMENTS 🌸

  • idmap β€” idmap of the mount. literally just which idmapping this mount is rolling with 🌈
  • dentry β€” pointer to the affected dentry. this is the one that just had its acl removed, so keep your eyes on it πŸ‘€
  • acl_name β€” name of the posix acl. which acl we're talking about, name-wise πŸ’«

πŸ‘‘ DESCRIPTION πŸ‘‘

Update the 'security.evm' xattr with the EVM HMAC re-calculated after removing posix acls.

that's it, that's the whole gig. the acl got removed, the old HMAC is now a liar, so this function recalculates it and tucks it back into 'security.evm' so the integrity check doesn't have a crisis 😭πŸ”₯ it's the post-removal glow-up, periodt.


πŸŽ€ SEE ALSO πŸŽ€

the whole evm friend group, fr fr β€” go read them if you're obsessed πŸ§šπŸ’œ


ngl if you're touching this, you're probably already deep in security/integrity/evm and you know exactly why the HMAC has to be recomputed. slay. πŸ”₯

and that's the page!! source path is ./security/integrity/evm and the date on this bad boy is October 2026 β€” so yeah, future vibes only β­πŸ’– bye bestie, go keep those xattrs valid πŸ’…βœ¨

πŸ“¦ where this page comes from