fsverity_readahead(9)

💖 fsverity_readahead(9) — Kernel API Manual 💖

okay bestie, welcome to the fsverity_readahead(9) page — it’s giving kernel API realness, and we’re gonna get through it together ✨

---

🌸 NAME 🌸

fsverity_readahead — kick off readahead on fsverity hashes 🎀

---

🦋 SYNOPSIS 🦋

void fsverity_readahead (struct fsverity_info *vi , pgoff_t index , unsigned long nr_pages );

---

🎀 ARGUMENTS 🎀

• vi — the fsverity_info for the inode to be read, bestie 💅
• index — first file data page index that is being read ✨
• nr_pages — number of file data pages to be read 🫶

---

💜 DESCRIPTION 💜

So literally what happens is: start readahead on the fsverity hashes that are needed to verify the file data in the range from index to index + nr_pages (exclusive upper bound) 🔥

This is meant to be called from the file systems’ ->read_folio and ->readahead methods to ensure that the hashes are already cached on completion of the file data read if possible 🌈

it’s a “please have the hashes ready if you can” vibe, no cap 👑

---

⭐ SEE ALSO ⭐

• Kernel file ./fs/verity/verify.c
• fsverity_verify_blocks(9)
• fsverity_verify_bio(9)
• fsverity_enqueue_verify_work(9)

---

with love from ./fs/verity 🧚 source/version vibes: ./fs/verity; date: October 2026; page: fsverity_readahead(9) 💖