From: Damien Le Moal <dlemoal@kernel.org>
To: Jens Axboe <axboe@kernel.dk>,
linux-block@vger.kernel.org, dm-devel@lists.linux.dev,
Mike Snitzer <snitzer@kernel.org>,
Mikulas Patocka <mpatocka@redhat.com>
Cc: Christoph Hellwig <hch@lst.de>, Benjamin Marzinski <bmarzins@redhat.com>
Subject: [PATCH v3 1/2] block: Imporve checks on zone resource limits
Date: Wed, 5 Jun 2024 15:39:05 +0900 [thread overview]
Message-ID: <20240605063907.129120-2-dlemoal@kernel.org> (raw)
In-Reply-To: <20240605063907.129120-1-dlemoal@kernel.org>
Make sure that the zone resource limits of a zoned block device are
correct by checking that:
(a) If the device has a max active zones limit, make sure that the max
open zones limit is lower than the max active zones limit.
(b) If the device has zone resource limits, check that the limits
values are lower than the number of sequential zones of the device.
If it is not, assume that the zoned device has no limits by setting
the limits to 0.
For (a), a check is added to blk_validate_zoned_limits() and an error
returned if the max open zones limit exceeds the value of the max active
zone limit (if there is one).
For (b), given that we need to number of sequential zones of the device,
this check is added to disk_update_zone_resources(). This is safe to do
as that function is executed with the disk queue frozen and the check
executed after queue_limits_start_update() with the queue limits lock
held.
Signed-off-by: Damien Le Moal <dlemoal@kernel.org>
---
block/blk-settings.c | 8 ++++++++
block/blk-zoned.c | 17 ++++++++++++++---
2 files changed, 22 insertions(+), 3 deletions(-)
diff --git a/block/blk-settings.c b/block/blk-settings.c
index effeb9a639bb..474c709ea85b 100644
--- a/block/blk-settings.c
+++ b/block/blk-settings.c
@@ -80,6 +80,14 @@ static int blk_validate_zoned_limits(struct queue_limits *lim)
if (WARN_ON_ONCE(!IS_ENABLED(CONFIG_BLK_DEV_ZONED)))
return -EINVAL;
+ /*
+ * Given that active zones include open zones, the maximum number of
+ * open zones cannot be larger than the maximum numbber of active zones.
+ */
+ if (lim->max_active_zones &&
+ lim->max_open_zones > lim->max_active_zones)
+ return -EINVAL;
+
if (lim->zone_write_granularity < lim->logical_block_size)
lim->zone_write_granularity = lim->logical_block_size;
diff --git a/block/blk-zoned.c b/block/blk-zoned.c
index 52abebf56027..7a2dfbc8f614 100644
--- a/block/blk-zoned.c
+++ b/block/blk-zoned.c
@@ -1650,6 +1650,20 @@ static int disk_update_zone_resources(struct gendisk *disk,
if (!disk->zone_wplugs_pool)
return 0;
+ lim = queue_limits_start_update(q);
+
+ /*
+ * Some devices can advertize max open and max active zone limits that
+ * are larger than the number of sequential zones of the zoned block
+ * device, e.g. a small ZNS namespace. For such case, assume that the
+ * zoned device has no limits.
+ */
+ nr_seq_zones = disk->nr_zones - nr_conv_zones;
+ if (lim.max_active_zones > nr_seq_zones)
+ lim.max_active_zones = 0;
+ if (lim.max_open_zones > nr_seq_zones)
+ lim.max_open_zones = 0;
+
/*
* If the device has no limit on the maximum number of open and active
* zones, set its max open zone limit to the mempool size to indicate
@@ -1657,9 +1671,6 @@ static int disk_update_zone_resources(struct gendisk *disk,
* dynamic zone write plug allocation when simultaneously writing to
* more zones than the size of the mempool.
*/
- lim = queue_limits_start_update(q);
-
- nr_seq_zones = disk->nr_zones - nr_conv_zones;
pool_size = max(lim.max_open_zones, lim.max_active_zones);
if (!pool_size)
pool_size = min(BLK_ZONE_WPLUG_DEFAULT_POOL_SIZE, nr_seq_zones);
--
2.45.1
next prev parent reply other threads:[~2024-06-05 6:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-05 6:39 [PATCH v3 0/2] Fix DM zone resource limits stacking Damien Le Moal
2024-06-05 6:39 ` Damien Le Moal [this message]
2024-06-05 6:45 ` [PATCH v3 1/2] block: Imporve checks on zone resource limits Christoph Hellwig
2024-06-05 6:46 ` Damien Le Moal
2024-06-05 6:39 ` [PATCH v3 2/2] dm: Improve zone resource limits handling Damien Le Moal
2024-06-05 6:49 ` Christoph Hellwig
2024-06-05 6:55 ` 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=20240605063907.129120-2-dlemoal@kernel.org \
--to=dlemoal@kernel.org \
--cc=axboe@kernel.dk \
--cc=bmarzins@redhat.com \
--cc=dm-devel@lists.linux.dev \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--cc=mpatocka@redhat.com \
--cc=snitzer@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