evm_fix_hmac(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ¦‹ bestie, meet evm_fix_hmac(9) πŸ¦‹

okay so this is the section 9 Kernel API Manual page for evm_fix_hmac, and it is lowkey very "kernel integrity internals" of it all. We're gonna get through it together, no cap. πŸ’–

🌸 NAME 🌸

evm_fix_hmac β€” calculates the HMAC and adds it to security.evm for fix mode. That's the whole vibe: HMAC math, then it goes into security.evm because we're in fix mode. ✨

✨ SYNOPSIS ✨

int evm_fix_hmac (struct dentry *dentry , const char *xattr_name , const
       char *xattr_value , size_t xattr_value_len );

πŸŽ€ ARGUMENTS πŸŽ€

  • dentry β€” pointer to the affected dentry which doesn't yet have security.evm xattr. So like, this is the dentry in question, and it has not gotten its security.evm xattr yet. 🫢
  • xattr_name β€” pointer to the affected extended attribute name. The name of the xattr that's in the mix.
  • xattr_value β€” pointer to the new extended attribute value. The fresh value, bestie.
  • xattr_value_len β€” pointer to the new extended attribute value length. Yep, that's the length situation exactly as the page spells it out.

πŸ’… DESCRIPTION πŸ’…

Expects to be called with i_mutex locked.

⚠️ okay important vibe check: this page says it expects to be called with i_mutex locked. So do not come in here unlocked and act surprised, bestie. The manual is telling you the expectation up front. πŸ”’

πŸ”₯ RETURN πŸ”₯

  • 0 on success. Slay, it worked. βœ…
  • -EPERM / -ENOMEM / -EOPNOTSUPP on failure. Those are the failure returns, and they are not cute. 😭

🌈 SEE ALSO 🌈

Kernel file: ./security/integrity/evm/evm_main.c


Signed off from ./security/integrity/evm, dated October 2026, and filed under evm_fix_hmac(9) β€” bye bestie, go lock that i_mutex πŸ’…βœ¨

πŸ“¦ where this page comes from