From: Niklas Cassel <cassel@kernel.org>
To: Stefan Hajnoczi <stefanha@redhat.com>,
Kevin Wolf <kwolf@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
Hanna Reitz <hreitz@redhat.com>
Cc: Sam Li <faithilikerun@gmail.com>,
Damien Le Moal <dlemoal@kernel.org>,
Niklas Cassel <cassel@kernel.org>,
qemu-block@nongnu.org, qemu-devel@nongnu.org
Subject: [PATCH v3 05/12] virtio-blk: check the write granularity of writes to sequential zones
Date: Fri, 4 Sep 2026 18:17:53 +0200 [thread overview]
Message-ID: <20260904161801.1568841-6-cassel@kernel.org> (raw)
In-Reply-To: <20260904161801.1568841-1-cassel@kernel.org>
All VIRTIO_BLK_T_OUT requests issued to sequential zones and all
VIRTIO_BLK_T_ZONE_APPEND requests must have an offset and a data size
that are multiples of the write granularity reported by the device
(virtio 1.4, 5.2.6.1), and a violation is reported as
VIRTIO_BLK_S_ZONE_UNALIGNED_WP (virtio 1.4, 5.2.6).
Neither request type was fully checked. Zone appends validated only the
offset, while writes were not checked at all.
Check the size of the appended data, and both the offset and the size of
a write, against blkconf_zone_write_granularity(), so that every request the
device accepts is one that the guest driver was told is valid. Writes to
conventional zones keep no alignment constraint beyond the logical block
size. The write path performs the check after virtio_blk_sect_range_ok()
so that the zone index derived from the guest supplied sector is known to
be in range.
Signed-off-by: Niklas Cassel <cassel@kernel.org>
---
hw/block/virtio-blk.c | 38 +++++++++++++++++++++++++++++++++++++-
1 file changed, 37 insertions(+), 1 deletion(-)
diff --git a/hw/block/virtio-blk.c b/hw/block/virtio-blk.c
index f6781ff5f6..7d5a02a42c 100644
--- a/hw/block/virtio-blk.c
+++ b/hw/block/virtio-blk.c
@@ -398,6 +398,33 @@ static bool virtio_blk_sect_range_ok(VirtIOBlock *dev,
return true;
}
+/*
+ * Both the offset and the size of a write to a sequential zone must be a
+ * multiple of the write granularity that the device reports. Conventional
+ * zones are not constrained. The zone index is derived from a guest supplied
+ * sector, so this must only be called once virtio_blk_sect_range_ok() has
+ * bounded it.
+ */
+static bool virtio_blk_zone_write_granularity_ok(VirtIOBlock *dev,
+ uint64_t sector, size_t size)
+{
+ BlockDriverState *bs = blk_bs(dev->blk);
+ uint64_t offset = sector << BDRV_SECTOR_BITS;
+ uint32_t wg_mask;
+
+ if (bs->bl.zoned == BLK_Z_NONE) {
+ return true;
+ }
+
+ if (BDRV_ZT_IS_CONV(bs->wps->wp[bdrv_zone_index(bs, offset)])) {
+ return true;
+ }
+
+ wg_mask = blkconf_zone_write_granularity(&dev->conf.conf) - 1;
+
+ return !(offset & wg_mask) && !(size & wg_mask);
+}
+
static uint8_t virtio_blk_handle_discard_write_zeroes(VirtIOBlockReq *req,
struct virtio_blk_discard_write_zeroes *dwz_hdr, bool is_write_zeroes)
{
@@ -522,7 +549,7 @@ static bool check_zoned_request(VirtIOBlock *s, int64_t offset, int64_t len,
if (append) {
uint32_t wg_mask = blkconf_zone_write_granularity(&s->conf.conf) - 1;
- if (offset & wg_mask) {
+ if (offset & wg_mask || len & wg_mask) {
*status = VIRTIO_BLK_S_ZONE_UNALIGNED_WP;
return false;
}
@@ -911,6 +938,15 @@ static int virtio_blk_handle_request(VirtIOBlockReq *req, MultiReqBuffer *mrb)
return 0;
}
+ if (is_write &&
+ !virtio_blk_zone_write_granularity_ok(s, req->sector_num,
+ req->qiov.size)) {
+ virtio_blk_req_complete(req, VIRTIO_BLK_S_ZONE_UNALIGNED_WP);
+ block_acct_invalid(blk_get_stats(s->blk), BLOCK_ACCT_WRITE);
+ g_free(req);
+ return 0;
+ }
+
block_acct_start(blk_get_stats(s->blk), &req->acct, req->qiov.size,
is_write ? BLOCK_ACCT_WRITE : BLOCK_ACCT_READ);
--
2.55.0
next prev parent reply other threads:[~2026-09-04 16:20 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-04 16:17 [PATCH v3 00/12] block: fix the zone write granularity and the zone append limit Niklas Cassel
2026-09-04 16:17 ` [PATCH v3 01/12] block: widen BlockLimits.zone_size to uint64_t Niklas Cassel
2026-09-04 16:17 ` [PATCH v3 02/12] virtio-blk: do not merge requests across a zone boundary Niklas Cassel
2026-09-04 16:17 ` [PATCH v3 03/12] block: add a helper for the index of the zone an offset falls in Niklas Cassel
2026-09-05 0:32 ` Damien Le Moal
2026-09-04 16:17 ` [PATCH v3 04/12] virtio-blk: report the effective zone write granularity Niklas Cassel
2026-09-04 16:17 ` Niklas Cassel [this message]
2026-09-05 0:33 ` [PATCH v3 05/12] virtio-blk: check the write granularity of writes to sequential zones Damien Le Moal
2026-09-04 16:17 ` [PATCH v3 06/12] hw/block: reject a zoned device whose write pointers are unaddressable Niklas Cassel
2026-09-05 0:34 ` Damien Le Moal
2026-09-04 16:17 ` [PATCH v3 07/12] block: reject zone appends that are not a multiple of the sector size Niklas Cassel
2026-09-04 16:17 ` [PATCH v3 08/12] file-posix: remove the zone append write granularity check Niklas Cassel
2026-09-04 16:17 ` [PATCH v3 09/12] file-posix: base the zone append limit on the transfer limit Niklas Cassel
2026-09-04 16:17 ` [PATCH v3 10/12] virtio-blk: derive the maximum zone append size Niklas Cassel
2026-09-04 16:17 ` [PATCH v3 11/12] file-posix: reject a zone append past the device capacity Niklas Cassel
2026-09-04 16:18 ` [PATCH v3 12/12] file-posix: reject a zone append to a full or conventional zone Niklas Cassel
2026-09-05 0:38 ` Damien Le Moal
2026-09-07 10:47 ` Niklas Cassel
2026-09-08 0:18 ` 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=20260904161801.1568841-6-cassel@kernel.org \
--to=cassel@kernel.org \
--cc=dlemoal@kernel.org \
--cc=faithilikerun@gmail.com \
--cc=hreitz@redhat.com \
--cc=kwolf@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.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 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.