From: Niklas Cassel <cassel@kernel.org>
To: Stefan Hajnoczi <stefanha@redhat.com>,
"Michael S. Tsirkin" <mst@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 05/12] virtio-blk: check the write granularity of writes to sequential zones
Date: Tue, 25 Aug 2026 22:57:40 +0200 [thread overview]
Message-ID: <20260825205748.679968-6-cassel@kernel.org> (raw)
In-Reply-To: <20260825205748.679968-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 | 25 ++++++++++++++++++++++++-
1 file changed, 24 insertions(+), 1 deletion(-)
diff --git a/hw/block/virtio-blk.c b/hw/block/virtio-blk.c
index f8cda1baa7..7977f4abe5 100644
--- a/hw/block/virtio-blk.c
+++ b/hw/block/virtio-blk.c
@@ -522,7 +522,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 +911,29 @@ 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_mask =
+ blkconf_zone_write_granularity(&s->conf.conf) - 1;
+
+ /*
+ * 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_mask || req->qiov.size & wg_mask) &&
+ !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-25 20:59 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-25 20:57 [PATCH 00/12] block: fix the zone write granularity and the zone append limit Niklas Cassel
2026-08-25 20:57 ` [PATCH 01/12] block: widen BlockLimits.zone_size to uint64_t Niklas Cassel
2026-08-28 5:58 ` Damien Le Moal
2026-08-25 20:57 ` [PATCH 02/12] virtio-blk: do not merge writes across a zone boundary Niklas Cassel
2026-08-28 6:02 ` Damien Le Moal
2026-08-25 20:57 ` [PATCH 03/12] file-posix: fix zone write granularity assignment for zoned block devices Niklas Cassel
2026-08-25 20:57 ` [PATCH 04/12] virtio-blk: report the effective zone write granularity Niklas Cassel
2026-08-28 6:03 ` Damien Le Moal
2026-08-25 20:57 ` Niklas Cassel [this message]
2026-08-28 6:07 ` [PATCH 05/12] virtio-blk: check the write granularity of writes to sequential zones Damien Le Moal
2026-08-28 6:09 ` Damien Le Moal
2026-08-25 20:57 ` [PATCH 06/12] hw/block: reject a zoned device whose write pointers are unaddressable Niklas Cassel
2026-08-28 6:12 ` Damien Le Moal
2026-08-25 20:57 ` [PATCH 07/12] block: reject zone appends that are not a multiple of the sector size Niklas Cassel
2026-08-28 6:13 ` Damien Le Moal
2026-08-25 20:57 ` [PATCH 08/12] file-posix: remove the zone append write granularity check Niklas Cassel
2026-08-28 6:14 ` Damien Le Moal
2026-08-25 20:57 ` [PATCH 09/12] file-posix: base the zone append limit on the transfer limit Niklas Cassel
2026-08-28 6:17 ` Damien Le Moal
2026-08-25 20:57 ` [PATCH 10/12] virtio-blk: derive the maximum zone append size Niklas Cassel
2026-08-28 6:18 ` Damien Le Moal
2026-08-25 20:57 ` [PATCH 11/12] file-posix: reject a zone append past the device capacity Niklas Cassel
2026-08-28 6:18 ` Damien Le Moal
2026-08-25 20:57 ` [PATCH 12/12] file-posix: reject a zone append to a full or conventional zone Niklas Cassel
2026-08-28 6:19 ` 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=20260825205748.679968-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.