blk_revalidate_disk_zones(9)

✨ blk_revalidate_disk_zones(9) ✨

okay bestie, welcome to the Kernel API Manual (section 9, obvs) — today we're talking about blk_revalidate_disk_zones, and honestly? she's kind of a big deal in the zoned-disk world 💅

---

🎀 NAME 🎀

blk_revalidate_disk_zones — the girl who (re)allocates and initializes zone write plugs. no cap, that's literally her whole thing 🫶

---

🌸 SYNOPSIS 🌸

int blk_revalidate_disk_zones (struct gendisk *disk );

---

💖 ARGUMENTS 💖

• disk — the target disk. that's it, that's the whole argument. main character vibes only 👑

---

🦋 DESCRIPTION 🦋

so listen 💫 — this is a helper function for low-level device drivers, and her job is to check, (re)allocate, and initialize all the resources used for managing zoned disks. she's the responsible one in the group chat fr fr.

normally, blk-mq based drivers should call her:

• when a zoned gendisk is probed, and
• when the zone configuration of the gendisk changes (e.g. after a format) ✨

⚠️ but babe, read this before you call her: the device driver must already have set the device zone size (the chunk_sector limit) and the max zone append limit before calling this function. like, that's a prerequisite, not a suggestion 😭

also, BIO based drivers can use this function too — iconic, inclusive, we love to see it 🌈 — as long as the device queue can be safely frozen 🧊. no frozen queue? no entry. periodt.

---

👑 SEE ALSO 👑

check out the kernel file ./block/blk-zoned.c and these besties:

• blk_zone_cond_str(9)
• bdev_zone_is_seq(9)
• blkdev_report_zones(9)
• blkdev_zone_mgmt(9)
• disk_report_zone(9)
• blkdev_get_zone_info(9)
• blkdev_report_zones_cached(9)
• blk_zone_plug_bio(9)
• blk_zone_issue_zeroout(9)

---

okay that's the whole page, ily, go call her responsibly 💜

🌸 signed, sealed, delivered from ./block — October 2026 — blk_revalidate_disk_zones(9) 🌸 slay 🎀✨