Linux block layer
 help / color / mirror / Atom feed
From: Hannes Reinecke <hare@suse.de>
To: Damien Le Moal <dlemoal@kernel.org>, Jens Axboe <axboe@kernel.dk>,
	linux-block@vger.kernel.org
Cc: Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH v3 08/13] block: propagate readonly and offline conditions to zone write plugs
Date: Tue, 11 Aug 2026 13:35:44 +0200	[thread overview]
Message-ID: <a5e58173-11ca-422a-b68e-0e574efc9e1c@suse.de> (raw)
In-Reply-To: <20260811105852.1245357-9-dlemoal@kernel.org>

On 8/11/26 12:58 PM, Damien Le Moal wrote:
> When revalidating the zones of a zoned block device, or when handling a
> zone which has a zone write plug flagged with
> BLK_ZONE_WPLUG_NEED_WP_UPDATE, the function
> disk_zone_wplug_sync_wp_offset() is used to update the write pointer
> offset of a zone write plug. However, this does not take into account the
> condition of the zone, which may have changed to readonly or offline,
> which in itself will always cause errors.
> 
> In order to catch such errors, rename disk_zone_wplug_sync_wp_offset() to
> disk_zone_wplug_sync_state() and in addition to the zone write pointer,
> also update the zone write plug condition if the zone is readonly or
> offline.
> 
> This change also requires changes to how a reset all zones operation
> (REQ_OP_ZONE_RESET_ALL) is handled so that the offline or read-only
> condition of zone write plugs is not overwritten with an erroneous empty
> condition. To do so, introduce the helper function
> disk_zone_is_offline_or_readonly() to skip updating the condition of zones
> that are read-only or offline and that do not have a zone write plug.
> For zones that have a zone write plug, the helper function
> disk_zone_wplug_is_offline_or_readonly() is used in
> disk_zone_wplug_set_wp_offset() to not update a zone write plug write
> pointer and condition for read-only and offline zones.
> 
> Signed-off-by: Damien Le Moal <dlemoal@kernel.org>
> Reviewed-by: Bart Van Assche <bvanassche@acm.org>
> ---
>   block/blk-zoned.c | 55 +++++++++++++++++++++++++++++++++++++++--------
>   1 file changed, 46 insertions(+), 9 deletions(-)
> 
Reviewed-by: Hannes Reinecke <hare@kernel.org>

Cheers,

Hannes
-- 
Dr. Hannes Reinecke                  Kernel Storage Architect
hare@suse.de                                +49 911 74053 688
SUSE Software Solutions GmbH, Frankenstr. 146, 90461 Nürnberg
HRB 36809 (AG Nürnberg), GF: I. Totev, A. McDonald, W. Knoblich

  reply	other threads:[~2026-08-11 11:35 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-11 10:58 [PATCH v3 00/13] Improve handling of offline and read-only zones Damien Le Moal
2026-08-11 10:58 ` [PATCH v3 01/13] block: remove disk_free_zone_resources() Damien Le Moal
2026-08-11 11:41   ` Johannes Thumshirn
2026-08-11 10:58 ` [PATCH v3 02/13] block: refactor disk_revalidate_zone_resources() Damien Le Moal
2026-08-11 11:46   ` Johannes Thumshirn
2026-08-11 10:58 ` [PATCH v3 03/13] block: refactor disk_update_zone_resources() Damien Le Moal
2026-08-11 11:28   ` Hannes Reinecke
2026-08-11 11:48   ` Johannes Thumshirn
2026-08-11 10:58 ` [PATCH v3 04/13] block: remember a zone type regardless of its condition Damien Le Moal
2026-08-11 11:29   ` Hannes Reinecke
2026-08-11 10:58 ` [PATCH v3 05/13] block: refactor bdev_zone_is_seq() Damien Le Moal
2026-08-11 11:30   ` Hannes Reinecke
2026-08-11 10:58 ` [PATCH v3 06/13] block: introduce disk_for_all_zone_wplugs() Damien Le Moal
2026-08-11 11:31   ` Hannes Reinecke
2026-08-11 10:58 ` [PATCH v3 07/13] block: drop all zone write plugs on capacity changes Damien Le Moal
2026-08-11 11:33   ` Hannes Reinecke
2026-08-11 10:58 ` [PATCH v3 08/13] block: propagate readonly and offline conditions to zone write plugs Damien Le Moal
2026-08-11 11:35   ` Hannes Reinecke [this message]
2026-08-11 10:58 ` [PATCH v3 09/13] block: always treat offline and read-only zones as dead Damien Le Moal
2026-08-11 11:36   ` Hannes Reinecke
2026-08-11 10:58 ` [PATCH v3 10/13] block: fail zone management operations to read-only and offline zones Damien Le Moal
2026-08-11 11:41   ` Hannes Reinecke
2026-08-11 12:13     ` Damien Le Moal
2026-08-11 12:16       ` Hannes Reinecke
2026-08-11 10:58 ` [PATCH v3 11/13] block: allow read-only and offline conventional zones Damien Le Moal
2026-08-11 11:43   ` Hannes Reinecke
2026-08-11 10:58 ` [PATCH v3 12/13] block: simplify disk_zone_set_cond() Damien Le Moal
2026-08-11 11:45   ` Hannes Reinecke
2026-08-11 10:58 ` [PATCH v3 13/13] block: flag zoned disks with GENHD_FL_NO_PART Damien Le Moal
2026-08-11 11:45   ` Hannes Reinecke

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=a5e58173-11ca-422a-b68e-0e574efc9e1c@suse.de \
    --to=hare@suse.de \
    --cc=axboe@kernel.dk \
    --cc=dlemoal@kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox