All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@redhat.com>
To: Niklas Cassel <cassel@kernel.org>
Cc: Kevin Wolf <kwolf@redhat.com>,
	"Michael S. Tsirkin" <mst@redhat.com>,
	Hanna Reitz <hreitz@redhat.com>, Sam Li <faithilikerun@gmail.com>,
	Damien Le Moal <dlemoal@kernel.org>,
	qemu-block@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [PATCH v4 05/12] virtio-blk: check the write granularity of writes to sequential zones
Date: Wed, 9 Sep 2026 14:31:27 -0400	[thread overview]
Message-ID: <20260909183127.GD20134@fedora> (raw)
In-Reply-To: <20260907110748.1868714-6-cassel@kernel.org>

[-- Attachment #1: Type: text/plain, Size: 1287 bytes --]

On Mon, Sep 07, 2026 at 01:07:40PM +0200, Niklas Cassel wrote:
> 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.
> 
> Reviewed-by: Damien Le Moal <dlemoal@kernel.org>
> Signed-off-by: Niklas Cassel <cassel@kernel.org>
> ---
>  hw/block/virtio-blk.c | 38 +++++++++++++++++++++++++++++++++++++-
>  1 file changed, 37 insertions(+), 1 deletion(-)

Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2026-09-09 18:32 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-07 11:07 [PATCH v4 00/12] block: fix the zone write granularity and the zone append limit Niklas Cassel
2026-09-07 11:07 ` [PATCH v4 01/12] block: widen BlockLimits.zone_size to uint64_t Niklas Cassel
2026-09-09 18:04   ` Stefan Hajnoczi
2026-09-07 11:07 ` [PATCH v4 02/12] virtio-blk: do not merge requests across a zone boundary Niklas Cassel
2026-09-07 11:07 ` [PATCH v4 03/12] block: add a helper for the index of the zone an offset falls in Niklas Cassel
2026-09-09 18:05   ` Stefan Hajnoczi
2026-09-07 11:07 ` [PATCH v4 04/12] virtio-blk: report the effective zone write granularity Niklas Cassel
2026-09-09 18:27   ` Stefan Hajnoczi
2026-09-07 11:07 ` [PATCH v4 05/12] virtio-blk: check the write granularity of writes to sequential zones Niklas Cassel
2026-09-09 18:31   ` Stefan Hajnoczi [this message]
2026-09-07 11:07 ` [PATCH v4 06/12] hw/block: reject a zoned device whose write pointers are unaddressable Niklas Cassel
2026-09-09 18:34   ` Stefan Hajnoczi
2026-09-07 11:07 ` [PATCH v4 07/12] block: reject zone appends that are not a multiple of the sector size Niklas Cassel
2026-09-09 18:37   ` Stefan Hajnoczi
2026-09-09 18:42   ` Stefan Hajnoczi
2026-09-07 11:07 ` [PATCH v4 08/12] file-posix: remove the zone append write granularity check Niklas Cassel
2026-09-09 18:38   ` Stefan Hajnoczi
2026-09-07 11:07 ` [PATCH v4 09/12] file-posix: base the zone append limit on the transfer limit Niklas Cassel
2026-09-09 18:43   ` Stefan Hajnoczi
2026-09-07 11:07 ` [PATCH v4 10/12] virtio-blk: derive the maximum zone append size Niklas Cassel
2026-09-09 18:52   ` Stefan Hajnoczi
2026-09-07 11:07 ` [PATCH v4 11/12] file-posix: reject a zone append past the device capacity Niklas Cassel
2026-09-09 18:53   ` Stefan Hajnoczi
2026-09-07 11:07 ` [PATCH v4 12/12] file-posix: reject a zone append to a full or conventional zone Niklas Cassel
2026-09-09 18:54   ` Stefan Hajnoczi
2026-09-09 18:58 ` [PATCH v4 00/12] block: fix the zone write granularity and the zone append limit Stefan Hajnoczi

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=20260909183127.GD20134@fedora \
    --to=stefanha@redhat.com \
    --cc=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 \
    /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.