From: Niklas Cassel <cassel@kernel.org>
To: 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 v2 07/11] file-posix: remove the zone append write granularity check
Date: Wed, 2 Sep 2026 21:44:18 +0200 [thread overview]
Message-ID: <20260902194423.759355-8-cassel@kernel.org> (raw)
In-Reply-To: <20260902194423.759355-1-cassel@kernel.org>
The check rejects a zone append whose individual iovec lengths are not
multiples of the zone write granularity. That is stricter than the
constraint it is meant to enforce, which applies to the size of the
request as a whole. A request whose total is properly aligned but which
is split across, say, a 512 byte and a 3584 byte iovec is refused here,
even though the iovec boundaries do not survive into the scatter gather
list that reaches the device.
Nor is the driver the right place to enforce it. The kernel and the
device validate writes to a sequential zone themselves, which is why the
same function already passes the request length down without comparing it
against BlockLimits.max_append_sectors. The sector granularity that holds
for every backend is now checked once in bdrv_co_zone_append(), and a
frontend enforces the granularity it advertises to its guest.
Drop the check. BlockLimits.write_granularity is now set in one place, by
this driver from the zone_write_granularity queue attribute, and read in
one place, by the frontend that reports it.
Reviewed-by: Damien Le Moal <dlemoal@kernel.org>
Signed-off-by: Niklas Cassel <cassel@kernel.org>
---
block/file-posix.c | 16 +---------------
1 file changed, 1 insertion(+), 15 deletions(-)
diff --git a/block/file-posix.c b/block/file-posix.c
index c0d6ee30e4..f267513a4e 100644
--- a/block/file-posix.c
+++ b/block/file-posix.c
@@ -3593,8 +3593,6 @@ raw_co_zone_append(BlockDriverState *bs,
BdrvRequestFlags flags) {
assert(flags == 0);
int64_t zone_size_mask = bs->bl.zone_size - 1;
- int64_t iov_len = 0;
- int64_t len = 0;
if (*offset & zone_size_mask) {
error_report("sector offset %" PRId64 " is not aligned to zone size "
@@ -3602,20 +3600,8 @@ raw_co_zone_append(BlockDriverState *bs,
return -EINVAL;
}
- int64_t wg = bs->bl.write_granularity;
- int64_t wg_mask = wg - 1;
- for (int i = 0; i < qiov->niov; i++) {
- iov_len = qiov->iov[i].iov_len;
- if (iov_len & wg_mask) {
- error_report("len of IOVector[%d] %" PRId64 " is not aligned to "
- "block size %" PRId64 "", i, iov_len, wg);
- return -EINVAL;
- }
- len += iov_len;
- }
-
trace_zbd_zone_append(bs, *offset >> BDRV_SECTOR_BITS);
- return raw_co_prw(bs, offset, len, qiov, QEMU_AIO_ZONE_APPEND, 0);
+ return raw_co_prw(bs, offset, qiov->size, qiov, QEMU_AIO_ZONE_APPEND, 0);
}
#endif
--
2.55.0
next prev parent reply other threads:[~2026-09-02 19:46 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-02 19:44 [PATCH v2 00/11] block: fix the zone write granularity and the zone append limit Niklas Cassel
2026-09-02 19:44 ` [PATCH v2 01/11] block: widen BlockLimits.zone_size to uint64_t Niklas Cassel
2026-09-02 19:44 ` [PATCH v2 02/11] virtio-blk: do not merge requests across a zone boundary Niklas Cassel
2026-09-02 19:44 ` [PATCH v2 03/11] virtio-blk: report the effective zone write granularity Niklas Cassel
2026-09-02 19:44 ` [PATCH v2 04/11] virtio-blk: check the write granularity of writes to sequential zones Niklas Cassel
2026-09-03 0:51 ` Damien Le Moal
2026-09-04 16:05 ` Niklas Cassel
2026-09-02 19:44 ` [PATCH v2 05/11] hw/block: reject a zoned device whose write pointers are unaddressable Niklas Cassel
2026-09-03 0:52 ` Damien Le Moal
2026-09-02 19:44 ` [PATCH v2 06/11] block: reject zone appends that are not a multiple of the sector size Niklas Cassel
2026-09-02 19:44 ` Niklas Cassel [this message]
2026-09-02 19:44 ` [PATCH v2 08/11] file-posix: base the zone append limit on the transfer limit Niklas Cassel
2026-09-02 19:44 ` [PATCH v2 09/11] virtio-blk: derive the maximum zone append size Niklas Cassel
2026-09-02 19:44 ` [PATCH v2 10/11] file-posix: reject a zone append past the device capacity Niklas Cassel
2026-09-02 19:44 ` [PATCH v2 11/11] file-posix: reject a zone append to a full or conventional zone Niklas Cassel
2026-09-04 15:06 ` Niklas Cassel
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=20260902194423.759355-8-cassel@kernel.org \
--to=cassel@kernel.org \
--cc=dlemoal@kernel.org \
--cc=faithilikerun@gmail.com \
--cc=hreitz@redhat.com \
--cc=kwolf@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.