From: Stefan Hajnoczi <stefanha@redhat.com>
To: Niklas Cassel <cassel@kernel.org>
Cc: Kevin Wolf <kwolf@redhat.com>, John Snow <jsnow@redhat.com>,
"Denis V. Lunev" <den@openvz.org>,
Hanna Reitz <hreitz@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
Sam Li <faithilikerun@gmail.com>,
Damien Le Moal <dlemoal@kernel.org>,
qemu-block@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [PATCH v6 05/15] hw/block: derive the zone write granularity from the block sizes
Date: Tue, 22 Sep 2026 14:58:19 -0400 [thread overview]
Message-ID: <20260922185819.GB340123@fedora> (raw)
In-Reply-To: <20260921142819.2916043-6-cassel@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 2298 bytes --]
On Mon, Sep 21, 2026 at 04:28:07PM +0200, Niklas Cassel wrote:
> For ZBC/ZAC devices the write granularity is the physical block size, so
> a 512e SMR disk exposed through a host_device backend has a logical block
> size of 512 and a zone write granularity of 4096. We told the guest
> driver 512 while raw_co_zone_append() rejects anything that is not 4096
> byte aligned, so the driver saw a plain I/O error for a request it had
> been told was valid.
>
> Report the larger of the logical and the physical block size instead.
> Both are properties of the device model, so the value that a guest is
> given does not change when it is migrated to a host whose disks differ,
> which a value taken from BlockLimits would. It is also what a guest
> derives for itself: blk_validate_zoned_limits() raises
> zone_write_granularity to the logical block size, and for a SCSI disk
> sd_zbc_read_zones() takes it from the physical block size.
>
> blkconf_blocksizes() rejects a logical block size larger than the
> physical block size, so this is the physical block size in practice. It
> is expressed as the larger of the two because that is the constraint
> which applies: a guest cannot issue a write finer than the logical block
> size, and the medium cannot take one finer than the physical block size.
>
> Add it as a helper next to blkconf_blocksizes(), since it is derived from
> a BlockConf, and use it for the zone append offset check in
> check_zoned_request(), which validated against bs->bl.write_granularity.
> The value reported to the driver and the value that requests are
> validated against then cannot drift apart. The helper cannot return zero
> because blkconf_blocksizes() always leaves a logical block size behind,
> so the check no longer needs to guard against an unset granularity.
>
> Fixes: 4f7366506a96 ("virtio-blk: add zoned storage emulation for zoned devices")
> Signed-off-by: Niklas Cassel <cassel@kernel.org>
> ---
> hw/block/block.c | 5 +++++
> hw/block/virtio-blk.c | 13 +++++++------
> include/block/block_int-common.h | 7 +++++++
> include/hw/block/block.h | 13 +++++++++++++
> 4 files changed, 32 insertions(+), 6 deletions(-)
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2026-09-22 18:59 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-21 14:28 [PATCH v6 00/15] block: fix the zone write granularity and the zone append limit Niklas Cassel
2026-09-21 14:28 ` [PATCH v6 01/15] block: widen BlockLimits.zone_size to uint64_t Niklas Cassel
2026-09-21 14:28 ` [PATCH v6 02/15] virtio-blk: do not merge requests across a zone boundary Niklas Cassel
2026-09-21 14:28 ` [PATCH v6 03/15] block: add a helper for the index of the zone an offset falls in Niklas Cassel
2026-09-21 14:28 ` [PATCH v6 04/15] block: add a helper to check if a zone is conventional Niklas Cassel
2026-09-22 18:55 ` Stefan Hajnoczi
2026-09-21 14:28 ` [PATCH v6 05/15] hw/block: derive the zone write granularity from the block sizes Niklas Cassel
2026-09-22 18:58 ` Stefan Hajnoczi [this message]
2026-09-21 14:28 ` [PATCH v6 06/15] virtio-blk: check the write granularity of writes to sequential zones Niklas Cassel
2026-09-21 14:28 ` [PATCH v6 07/15] hw/block: reject a zoned device that the block sizes cannot address Niklas Cassel
2026-09-22 19:01 ` Stefan Hajnoczi
2026-09-21 14:28 ` [PATCH v6 08/15] block: reject zone appends that are not a multiple of the sector size Niklas Cassel
2026-09-21 14:28 ` [PATCH v6 09/15] block: reject a zone append that is larger than a zone Niklas Cassel
2026-09-22 19:04 ` Stefan Hajnoczi
2026-09-21 14:28 ` [PATCH v6 10/15] file-posix: remove the zone append write granularity check Niklas Cassel
2026-09-21 14:28 ` [PATCH v6 11/15] virtio-blk: add a max-append-sectors property Niklas Cassel
2026-09-22 19:14 ` Stefan Hajnoczi
2026-09-21 14:28 ` [PATCH v6 12/15] block: remove BlockLimits.max_append_sectors Niklas Cassel
2026-09-22 19:16 ` Stefan Hajnoczi
2026-09-21 14:28 ` [PATCH v6 13/15] file-posix: reject a zone append past the device capacity Niklas Cassel
2026-09-21 14:28 ` [PATCH v6 14/15] file-posix: reject a zone append to a full or conventional zone Niklas Cassel
2026-09-21 14:28 ` [PATCH v6 15/15] block: do not use CoroutineIOCompletion to hold a return value Niklas Cassel
2026-10-06 13:15 ` [PATCH v6 00/15] block: fix the zone write granularity and the zone append limit 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=20260922185819.GB340123@fedora \
--to=stefanha@redhat.com \
--cc=cassel@kernel.org \
--cc=den@openvz.org \
--cc=dlemoal@kernel.org \
--cc=faithilikerun@gmail.com \
--cc=hreitz@redhat.com \
--cc=jsnow@redhat.com \
--cc=kwolf@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
/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.