fsverity_verify_blocks(9)

fsverity_verify_blocks(9) 💅

okay so bestie, this is fsverity_verify_blocks(9) from the Kernel API Manual, and it's giving “verify data in a folio” energy. no cap, let's go 🫶✨

💖 NAME 💖

fsverity_verify_blocks — verify data in a folio 🌸

✨ SYNOPSIS ✨

       bool fsverity_verify_blocks (struct fsverity_info *vi , struct folio
       *folio , size_t len , size_t offset );

🧾 ARGUMENTS 🧾

• vi — fsverity_info for the inode to be read 👀
• folio — the folio containing the data to verify 🦋
• len — the length of the data to verify in the folio
• offset — the offset of the data to verify in the folio

🔥 DESCRIPTION 🔥

Verify data that has just been read from a verity file. The data must be located in a pagecache folio that is still locked and not yet uptodate. The length and offset of the data must be Merkle tree block size aligned — literally non-negotiable, bestie 💅

okay so vibe check: locked folio, not yet uptodate, and aligned length + offset. that's the whole assignment. periodt. 🫶

🎀 RETURN 🎀

true if the data is valid, else false. simple as that, icon behavior ✨

🌈 SEE ALSO 🌈

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

okay bye bestie — this page comes from source/version ./fs/verity, dated October 2026, and it's fsverity_verify_blocks(9) from the Kernel API Manual 💖🫶🎀