ENUM BLK_ZONE_REPORT_FLAGS(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ NAME ✨

enum blk_zone_report_flags β€” the feature flags of reported zone descriptors πŸŽ€

okay so real quick, bestie, this page lives in the Kernel API Manual, and today we're learning about a lil enum that's basically the mood-ring of zone reporting πŸ’…


πŸ¦‹ SYNOPSIS πŸ¦‹

enum blk_zone_report_flags {
    BLK_ZONE_REP_CAPACITY ,
    BLK_ZONE_REP_CACHED

};

🌸 Constants 🌸

two constants, two vibes, let's get into it ✨

  • BLK_ZONE_REP_CAPACITY β€” output only. it's saying "hey, the zone descriptors in a zone report have a valid capacity field" 🫢 like it's valid, no cap.
  • BLK_ZONE_REP_CACHED β€” input only. it's saying the zone report should be generated using cached zone information πŸ‘‘ and in that case? the implicit open, explicit open and closed zone conditions all get reported with the BLK_ZONE_COND_ACTIVE condition. the way that one condition just absorbs three whole states, main character energy fr fr πŸ’€

🌈 SEE ALSO 🌈

  • the kernel file ./include/uapi/linux/blkzoned.h
  • enum blk_zone_type(9)
  • enum blk_zone_cond(9)
  • struct blk_zone(9)
  • struct blk_zone_report(9)
  • struct blk_zone_range(9)

go read those next, iykyk πŸ“šβœ¨


okay that's the whole page, bestie, you ate that πŸ“ this one's coming at you from ./include/uapi/linux, dated October 2026, and it's enum blk_zone_report_flags(9) signing off πŸ’–πŸ¦‹ periodt.

πŸ“¦ where this page comes from