ima_inode_post_setattr(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… ima_inode_post_setattr(9) πŸ’…

okay so this is the Kernel API Manual entry for ima_inode_post_setattr, and bestie, it’s short but it matters ✨


🌸 NAME 🌸

ima_inode_post_setattr β€” reflect file metadata changes


πŸ¦‹ SYNOPSIS πŸ¦‹

void ima_inode_post_setattr (struct mnt_idmap *idmap , struct dentry *dentry , int ia_valid );

πŸŽ€ ARGUMENTS πŸŽ€

  • idmap β€” the idmap of the mount the inode was found from. iykyk 🫢
  • dentry β€” pointer to the affected dentry, like the actual entry getting noticed πŸ‘€
  • ia_valid β€” for the UID and GID status. that’s the vibe check for this one πŸ’…

✨ DESCRIPTION ✨

so when a dentry’s metadata changes, that might mean we need to appraise something. yes really, metadata glow-ups can trigger appraisal 😭

this function gets called from notify_change, which expects the caller to lock the inode’s i_mutex.

bestie, lock that i_mutex β€” the caller is expected to do it, no cap πŸ”’

🌈 SEE ALSO 🌈


k bye, the source/version tag on this page is ./security/integrity/ima and the date is October 2026 β€” periodt, slay, and see u never πŸ’–πŸ«Ά

πŸ“¦ where this page comes from