blkdev_zone_mgmt(9)

💅 blkdev_zone_mgmt — from the Kernel API Manual (yes, the 9 section, we're fancy)

okay so bestie, picture this: you're deep in the kernel, you've got a zoned block device, and you need to tell a whole range of zones what to do with their lives. That's this function. Literally its whole personality.

---

✨ NAME ✨

blkdev_zone_mgmt — execute a zone management operation on a range of zones 🎀

---

🦋 SYNOPSIS 🦋

int blkdev_zone_mgmt (struct block_device *bdev , enum req_op op ,
sector_t sector , sector_t nr_sectors );

---

🌸 ARGUMENTS 🌸

• bdev — the target block device, aka the main character of this whole situation 💖
• op — the operation you want performed on the zones. Choose wisely, queen.
• sector — start sector of the first zone you're operating on. Where the drama begins.
• nr_sectors — number of sectors. Heads up: this should be at least the length of one zone and must be zone size aligned. No cap, that alignment is not optional 🙈

---

🔥 DESCRIPTION 🔥

So what it does: it performs the specified operation on the range of zones given by sector..sector+nr_sectors. Iconic, honestly.

Specifying the entire disk sector range? Valid. Totally fine. Slay. ✨ But — and this is the part where you pay attention — the specified range should not contain conventional zones. Just don't. It's giving chaos otherwise 💀

The operation you execute on each zone can be a zone reset, open, close or finish request. Four vibes, pick one 🫶

---

👑 SEE ALSO 👑

Kernel file ./block/blk-zoned.c, plus the whole friend group:

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

---

and that's the whole page, bestie 🌈 this little masterpiece lives in ./block, dated October 2026, and it's filed under blkdev_zone_mgmt(9) — go forth and manage those zones responsibly 💜🎀