From: Niklas Cassel <cassel@kernel.org>
To: "Michael S. Tsirkin" <mst@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
Kevin Wolf <kwolf@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 2/2] virtio-blk: check the write granularity of writes to sequential zones
Date: Wed, 19 Aug 2026 21:10:31 +0200 [thread overview]
Message-ID: <20260819191031.3001633-3-cassel@kernel.org> (raw)
In-Reply-To: <20260819191031.3001633-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 virtio_blk_write_granularity(), so that every request
the device accepts is one that the 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 | 24 +++++++++++++++++++++++-
1 file changed, 23 insertions(+), 1 deletion(-)
diff --git a/hw/block/virtio-blk.c b/hw/block/virtio-blk.c
index ef5581c1e6..b1be0e9eda 100644
--- a/hw/block/virtio-blk.c
+++ b/hw/block/virtio-blk.c
@@ -514,7 +514,7 @@ static bool check_zoned_request(VirtIOBlock *s, int64_t offset, int64_t len,
if (append) {
uint32_t wg = virtio_blk_write_granularity(s);
- if ((offset % wg) != 0) {
+ if ((offset % wg) != 0 || (len % wg) != 0) {
*status = VIRTIO_BLK_S_ZONE_UNALIGNED_WP;
return false;
}
@@ -903,6 +903,28 @@ static int virtio_blk_handle_request(VirtIOBlockReq *req, MultiReqBuffer *mrb)
return 0;
}
+ if (is_write) {
+ BlockDriverState *bs = blk_bs(s->blk);
+ int64_t offset = req->sector_num << BDRV_SECTOR_BITS;
+ uint32_t wg = virtio_blk_write_granularity(s);
+
+ /*
+ * Both the offset and the size of a write to a sequential zone
+ * must be a multiple of the write granularity reported by the
+ * device. Conventional zones are not constrained. The zone index
+ * is derived from a guest supplied sector, so this must come after
+ * virtio_blk_sect_range_ok() has bounded it.
+ */
+ if (bs->bl.zoned != BLK_Z_NONE &&
+ ((offset % wg) != 0 || (req->qiov.size % wg) != 0) &&
+ !BDRV_ZT_IS_CONV(bs->wps->wp[offset / bs->bl.zone_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-08-19 19:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-19 19:10 [PATCH 0/2] virtio-blk: improve zone write granularity handling Niklas Cassel
2026-08-19 19:10 ` [PATCH 1/2] virtio-blk: report the effective zone write granularity Niklas Cassel
2026-08-20 6:01 ` Damien Le Moal
2026-08-19 19:10 ` Niklas Cassel [this message]
2026-08-20 6:03 ` [PATCH 2/2] virtio-blk: check the write granularity of writes to sequential zones 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=20260819191031.3001633-3-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.