evm_inode_post_removexattr(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– evm_inode_post_removexattr(9) β€” the kernel API manual, but make it make sense πŸ’–

okay so bestie, this is evm_inode_post_removexattr(9) from the Kernel API Manual, and it is literally the cleanup bestie of the xattr world. let me tell you everything, no cap 🫢


✨ NAME ✨

evm_inode_post_removexattr β€” update security.evm after removing the xattr

like, the whole entire job is: xattr got yeeted, now go fix up security.evm. that's it. that's the gig. πŸ’…


🌸 SYNOPSIS 🌸

void evm_inode_post_removexattr (struct dentry *dentry , const char *xattr_name );

returns void, so no exit status to stress about, she just does the thing and leaves ✨


πŸŽ€ ARGUMENTS πŸŽ€

  • dentry β€” pointer to the affected dentry. yes, this is the one that got its xattr removed, keep up bestie πŸ¦‹
  • xattr_name β€” pointer to the affected extended attribute name. the name of the xattr that dipped πŸ‘‹

πŸ’… DESCRIPTION πŸ’…

Update the HMAC stored in security.evm to reflect removal of the xattr. that's the whole vibe check β€” the HMAC is sitting there in security.evm thinking everything's fine, and this function is like "girl, the xattr is gone, let me update you" 🫢

no need to take the i_mutex lock here, bestie β€” this function is called from vfs_removexattr, which already takes the i_mutex. so it's lowkey already handled, do NOT go grabbing locks you don't need, that's not the move 😭

πŸ‘‘ SEE ALSO πŸ‘‘

the whole friend group, fr fr 🌈


okay that's the page!! it lives in ./security/integrity/evm, dated October 2026 β€” so like, future energy, main character timestamp. mwah, go read the source bestie πŸ’œπŸ’–πŸŽ€

πŸ“¦ where this page comes from