All of lore.kernel.org
 help / color / mirror / Atom feed
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 v6 13/15] file-posix: reject a zone append past the device capacity
Date: Mon, 21 Sep 2026 16:28:15 +0200	[thread overview]
Message-ID: <20260921142819.2916043-14-cassel@kernel.org> (raw)
In-Reply-To: <20260921142819.2916043-1-cassel@kernel.org>

raw_co_zone_append() checks that the offset it is given is aligned to the
zone size, but not that it names a zone of the device. raw_co_prw() then
derives a zone index from it and reads that entry of the write pointer
array, so an offset past the end of the device reads past the end of the
array.

bdrv_co_zone_append() does not catch it either: bdrv_check_qiov_request()
bounds the request against BDRV_MAX_LENGTH, which has nothing to do with
the size of this device. A guest cannot reach it, because
check_zoned_request() in virtio-blk rejects an out of range offset first,
but qemu-io and any other caller of blk_co_zone_append() can:

  $ qemu-io --image-opts -n driver=host_device,filename=/dev/nullb0 \
        -c "zap -p 0x100000000000 0x1000"
  Segmentation fault

On a null_blk device with 1000 zones of 256 MiB, that offset yields zone
index 65536 and reads 512 KiB beyond an 8000 byte allocation.

Reject an offset that lies outside the device. That also bounds the
zone index that raw_co_prw() derives from it, so its write pointer
lookup stays inside the array.

Fixes: 4751d09adcc3 ("block: introduce zone append write for zoned devices")
Reviewed-by: Damien Le Moal <dlemoal@kernel.org>
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
Signed-off-by: Niklas Cassel <cassel@kernel.org>
---
 block/file-posix.c | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/block/file-posix.c b/block/file-posix.c
index 1a4ca9d942..e1e6a03b25 100644
--- a/block/file-posix.c
+++ b/block/file-posix.c
@@ -3587,8 +3587,15 @@ raw_co_zone_append(BlockDriverState *bs,
                    QEMUIOVector *qiov,
                    BdrvRequestFlags flags) {
     assert(flags == 0);
+    int64_t capacity = bs->total_sectors << BDRV_SECTOR_BITS;
     int64_t zone_size_mask = bs->bl.zone_size - 1;
 
+    if (*offset >= capacity) {
+        error_report("*offset %" PRId64 " is equal to or greater than the "
+                     "device capacity %" PRId64 "", *offset, capacity);
+        return -ENOSPC;
+    }
+
     if (*offset & zone_size_mask) {
         error_report("sector offset %" PRId64 " is not aligned to zone size "
                      "%" PRId64 "", *offset / 512, bs->bl.zone_size / 512);
-- 
2.55.0



  parent reply	other threads:[~2026-09-21 14:30 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
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 ` Niklas Cassel [this message]
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=20260921142819.2916043-14-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.