From: Damien Le Moal <dlemoal@kernel.org>
To: linux-block@vger.kernel.org, Jens Axboe <axboe@kernel.dk>,
linux-nvme@lists.infradead.org, Christoph Hellwig <hch@lst.de>,
Keith Busch <kbusch@kernel.org>,
linux-scsi@vger.kernel.org,
"Martin K . Petersen" <martin.petersen@oracle.com>
Subject: [PATCH 0/5] Improve checks in blk_revalidate_disk_zones()
Date: Thu, 29 Jun 2023 15:25:57 +0900 [thread overview]
Message-ID: <20230629062602.234913-1-dlemoal@kernel.org> (raw)
This series slightly modifies the 4 block device drivers that support
zoned block devices to ensure that they all call
blk_revalidate_disk_zones() with the zone size and max zone append
limits set. This is done in the first 4 patches.
With these changes, the last patch improves blk_revalidate_disk_zones()
to better check a zoned device zones and the device limits.
Damien Le Moal (5):
scsi: sd_zbc: Set zone limits before revalidating zones
nvme: zns: Set zone limits before revalidating zones
block: nullblk: Set zone limits before revalidating zones
block: virtio_blk: Set zone limits before revalidating zones
block: improve checks in blk_revalidate_disk_zones()
block/blk-zoned.c | 99 +++++++++++++++++++++-------------
drivers/block/null_blk/zoned.c | 21 +++-----
drivers/block/virtio_blk.c | 35 ++++++------
drivers/nvme/host/zns.c | 9 ++--
drivers/scsi/sd_zbc.c | 12 ++---
5 files changed, 96 insertions(+), 80 deletions(-)
--
2.41.0
next reply other threads:[~2023-06-29 6:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-29 6:25 Damien Le Moal [this message]
2023-06-29 6:25 ` [PATCH 1/5] scsi: sd_zbc: Set zone limits before revalidating zones Damien Le Moal
2023-06-29 6:25 ` [PATCH 2/5] nvme: zns: " Damien Le Moal
2023-06-29 6:26 ` [PATCH 3/5] block: nullblk: " Damien Le Moal
2023-06-29 6:26 ` [PATCH 4/5] block: virtio_blk: " Damien Le Moal
2023-06-29 6:26 ` [PATCH 5/5] block: improve checks in blk_revalidate_disk_zones() Damien Le Moal
2023-06-29 17:27 ` [PATCH 0/5] Improve " Bart Van Assche
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=20230629062602.234913-1-dlemoal@kernel.org \
--to=dlemoal@kernel.org \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
/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