fsverity_active(9)

💖 fsverity_active(9) — a Kernel API Manual moment 💖

okay so bestie, welcome to fsverity_active(9) from the Kernel API Manual, and honestly? this tiny little function is doing the most for file integrity and we're gonna talk about it 🫶

---

✨ NAME ✨

fsverity_active — the vibes check that answers: do reads from the inode need to go through fs-verity? 👀

---

🌸 SYNOPSIS 🌸

bool fsverity_active (const struct inode *inode );

literally that's the whole signature, she's compact and she knows it 💅

---

🎀 ARGUMENTS 🎀

• inode — the inode to check 🦋 that's it, that's the argument, no cap

---

🧚 DESCRIPTION 🧚

so what does she do, you ask? she checks whether the inode's verity info has been set, and whether reads need to verify the file data. that's the whole assignment and she ate 🔥

like, it's giving "am I supposed to be doing the extra verify step or not" energy, and she is the one who tells you 🙈

---

⭐ RETURN ⭐

• true — if reads need to go through fs-verity ✅
• otherwise false — nope, no fs-verity detour for these reads 💀

---

🌈 SEE ALSO 🌈

• Kernel file ./include/linux/fsverity.h
• fsverity_get_info(9)
• fsverity_file_open(9)

go read those too bestie, iykyk 📚✨

---

lowkey reminder: this page lives in ./include/linux, dated October 2026, and it's page fsverity_active(9) — mwah, slay, periodt 💜👑