folio_zero_range(9)

📦 version 7.3.1, in nixpkgs unstable

💅 folio_zero_range — from the Kernel API Manual (section 9, bestie)

okay so picture this: you've got a folio, right? and you just need a lil chunk of it to be zeros. not the whole thing, just some bytes. that's literally this function. it's giving "selective erasure" and honestly? iconic. ✨

🌸 NAME 🌸

folio_zero_range — zero a byte range in a folio. that's it. that's the whole job. no cap. 💖

✨ SYNOPSIS ✨

void folio_zero_range (struct folio *folio , size_t start , size_t
length );

like, look at her. void return, three args, no drama. she's not gonna tell you if it worked — she just does it. main character energy fr fr. 🫶

🎀 ARGUMENTS 🎀

  • folio — the folio you're writing to. this is the vibe check target, the thing getting zeroed. your canvas, your main squeeze. 🦋
  • start — the first byte to zero. like, where the zeroing begins. the starting line. the "we begin here" of it all. ⭐
  • length — the number of bytes to zero. how many bytes get the treatment. the size of the zero party. 🌈

so between start and start + length, everything becomes zero. that's the tea. 🍓

⚠️ heads up bestie: this page does not hand you a return value, because the function is void. it also doesn't promise anything about errors here — so don't go inventing guarantees that aren't on the page, iykyk. 💀

👑 SEE ALSO 👑

the kernel file in question lives at ./include/linux/highmem.h, and the whole highmem/highpage extended universe is right here — go be nosy, it's a whole friend group:

💜 one folio, one range, zero bytes. go off, bestie.

that's the whole page, babes — brought to you by the ./include/linux directory, dated October 2026, and delivered in true folio_zero_range(9) fashion. mwah 💅🎀✨🔥

📦 where this page comes from