From: Damien Le Moal <dlemoal@kernel.org>
To: Jens Axboe <axboe@kernel.dk>, linux-block@vger.kernel.org
Cc: Christoph Hellwig <hch@lst.de>
Subject: [PATCH v5 00/13] Improve handling of offline and read-only zones
Date: Fri, 14 Aug 2026 22:47:37 +0900 [thread overview]
Message-ID: <20260814134750.2100304-1-dlemoal@kernel.org> (raw)
Jens,
This patch series refactor some zone related code and improves the
caching iof zone information and the management of zone write plugs in
preparation for fully supporting storage element depopulation.
Most of the functional changes here are around the management of zone
write plugs to better handle read-only and offline zones as these
conditions can become more common with storage element being depopulated.
Changes from v4:
- Renamed bdev_check_zone_mgmt() to bdev_zone_mgmt_allowed() in patch 10
- Added Fixes tag to patch 13
- Added review tags
Changes from v3:
- Rebased on latest block/for-next
- Small modification to patch 4 to address Sashiko review comments
complaining about the potential for out of bound accesses to the zone
state array.
- Added review tags
Changes from v2:
- Minor changes to patches 1, 5, 7 and 8 to address some of the Sashiko
review comments (a lot of these comments point to cases that cannot
happen in practice or that are non-fatal and would generate errors due
to a user invalid use of the device).
- Applied review tags
Changes from v1:
- Fixup error path change in patch 1
- Use WARN_ON_ONCE in patch 4
- Dropped patch 14
- Applied review tags
Damien Le Moal (13):
block: remove disk_free_zone_resources()
block: refactor disk_revalidate_zone_resources()
block: refactor disk_update_zone_resources()
block: remember a zone type regardless of its condition
block: refactor bdev_zone_is_seq()
block: introduce disk_for_all_zone_wplugs()
block: drop all zone write plugs on capacity changes
block: propagate readonly and offline conditions to zone write plugs
block: always treat offline and read-only zones as dead
block: fail zone management operations to read-only and offline zones
block: allow read-only and offline conventional zones
block: simplify disk_zone_set_cond()
block: flag zoned disks with GENHD_FL_NO_PART
block/blk-core.c | 7 +-
block/blk-zoned.c | 791 +++++++++++++++++++++++++----------------
block/blk.h | 6 +
block/genhd.c | 7 +
include/linux/blkdev.h | 2 +-
5 files changed, 499 insertions(+), 314 deletions(-)
base-commit: 413ba2c89c48abdd0bafd5115806d43e1f414df5
--
2.55.0
next reply other threads:[~2026-08-14 13:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-14 13:47 Damien Le Moal [this message]
2026-08-14 13:47 ` [PATCH v5 01/13] block: remove disk_free_zone_resources() Damien Le Moal
2026-08-14 13:47 ` [PATCH v5 02/13] block: refactor disk_revalidate_zone_resources() Damien Le Moal
2026-08-14 13:47 ` [PATCH v5 03/13] block: refactor disk_update_zone_resources() Damien Le Moal
2026-08-14 13:47 ` [PATCH v5 04/13] block: remember a zone type regardless of its condition Damien Le Moal
2026-08-14 13:47 ` [PATCH v5 05/13] block: refactor bdev_zone_is_seq() Damien Le Moal
2026-08-14 13:47 ` [PATCH v5 06/13] block: introduce disk_for_all_zone_wplugs() Damien Le Moal
2026-08-14 13:47 ` [PATCH v5 07/13] block: drop all zone write plugs on capacity changes Damien Le Moal
2026-08-14 13:47 ` [PATCH v5 08/13] block: propagate readonly and offline conditions to zone write plugs Damien Le Moal
2026-08-14 13:47 ` [PATCH v5 09/13] block: always treat offline and read-only zones as dead Damien Le Moal
2026-08-14 13:47 ` [PATCH v5 10/13] block: fail zone management operations to read-only and offline zones Damien Le Moal
2026-08-14 13:47 ` [PATCH v5 11/13] block: allow read-only and offline conventional zones Damien Le Moal
2026-08-14 13:47 ` [PATCH v5 12/13] block: simplify disk_zone_set_cond() Damien Le Moal
2026-08-14 13:47 ` [PATCH v5 13/13] block: flag zoned disks with GENHD_FL_NO_PART Damien Le Moal
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260814134750.2100304-1-dlemoal@kernel.org \
--to=dlemoal@kernel.org \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.