ima_inode_post_setattr(9)
π
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 π
- Kernel file
./security/integrity/ima/ima_appraise.c validate_hash_algo(9)
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
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms