ipe_inode_setintegrity(9)

💖 NAME 💖

Okay bestie, welcome to the ipe_inode_setintegrity(9) page from the Kernel API Manual 💅✨. This one is literally about saving integrity data from an inode into IPE's LSM blob. No cap.

---

🦋 SYNOPSIS 🦋

int ipe_inode_setintegrity (const struct inode *inode , enum
lsm_integrity_type type , const void *value , size_t size );

---

🎀 ARGUMENTS 🎀

• inode — the inode you're sourcing the security blob from, bestie.
• type — supplies the integrity type. Yes, the type is doing its little vibe check here.
• value — the value that gets stored.
• size — the size of value. Gotta know how big it is, obviously.

---

✨ DESCRIPTION ✨

So this hook is currently used to save the existence of a validated fs-verity builtin signature into the LSM blob. That's the current gig — a validated fs-verity builtin signature exists, and the LSM blob gets to remember that. It's giving "small but crucial" energy, honestly 🫶.

---

🔥 RETURN 🔥

• 0 on success. Slay 💅.
• If an error occurs, the function will return the -errno. Like a little negative error-number receipt. Iykyk 😭.

---

🌈 SEE ALSO 🌈

Kernel file ./security/ipe/hooks.c, plus these iconic friends:

• ipe_bprm_check_security(9)
• ipe_bprm_creds_for_exec(9)
• ipe_mmap_file(9)
• ipe_file_mprotect(9)
• ipe_kernel_read_file(9)
• ipe_kernel_load_data(9)
• ipe_unpack_initramfs(9)
• ipe_bdev_free_security(9)
• ipe_bdev_setintegrity(9)

---

And that's the whole page, bestie 🫶. This lil manual comes from ./security/ipe and is dated October 2026 — the title stays ipe_inode_setintegrity(9), periodt 💖.