All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@redhat.com>
To: Fiona Ebner <f.ebner@proxmox.com>
Cc: qemu-devel@nongnu.org, qemu-block@nongnu.org, hreitz@redhat.com,
	kwolf@redhat.com, fam@euphon.net
Subject: Re: [PATCH 4/6] block/io: safeguard max transfer calculation in bdrv_aligned_pwritev()
Date: Mon, 19 Jan 2026 14:34:52 -0500	[thread overview]
Message-ID: <20260119193452.GC834718@fedora> (raw)
In-Reply-To: <20260109120837.2772961-5-f.ebner@proxmox.com>

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

On Fri, Jan 09, 2026 at 01:08:31PM +0100, Fiona Ebner wrote:
> This partially fixes iotest 177 with qcow2, where max_transfer is
> 64KiB, but the cluster size and thus pwrite_zeroes_alignment is 1MiB.
> Previously, max_transfer would be calculated as 0, triggering an
> assertion later.
> 
> Signed-off-by: Fiona Ebner <f.ebner@proxmox.com>
> ---
>  block/io.c | 6 ++++--
>  1 file changed, 4 insertions(+), 2 deletions(-)
> 
> diff --git a/block/io.c b/block/io.c
> index 12dc153573..233b2617ea 100644
> --- a/block/io.c
> +++ b/block/io.c
> @@ -2087,8 +2087,10 @@ bdrv_aligned_pwritev(BdrvChild *child, BdrvTrackedRequest *req,
>      assert(is_power_of_2(align));
>      assert((offset & (align - 1)) == 0);
>      assert((bytes & (align - 1)) == 0);
> -    max_transfer = QEMU_ALIGN_DOWN(MIN_NON_ZERO(bs->bl.max_transfer, INT_MAX),
> -                                   align);
> +    max_transfer = MIN_NON_ZERO(bs->bl.max_transfer, INT_MAX);
> +    if (max_transfer > align) {
> +        max_transfer = QEMU_ALIGN_DOWN(max_transfer, align);
> +    }

max_transfer < align seems paradoxical. It's a situation where the
largest allowed I/O request cannot meet alignment requirements.

Every other place that uses max_transfer in QEMU would also need to cope
with this.

block/blkdebug.c:blkdebug_open() fails if max_transfer is not aligned,
indicating that there are assumptions at least in some places that
max_transfer is aligned.

I hesitate to make this change because I fear it will break more things.
Why was max_transfer 64KB while pwrite_zeroes_alignment was 1MiB? Either
max_transfer should fit the alignment or pwrite_zeroes code needs to
distinguish between actual write zeroes operations and read-write-modify
I/O (which is plain read/write and not subject to
pwrite_zeroes_alignment).

Stefan

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

  reply	other threads:[~2026-01-19 19:36 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-09 12:08 [RFC v2 0/6] block/io: avoid failure caused by misaligned BLKZEROOUT ioctl Fiona Ebner
2026-01-09 12:08 ` [PATCH 1/6] block/io: pass alignment to bdrv_init_padding() Fiona Ebner
2026-01-09 12:08 ` [PATCH 2/6] block/io: add 'bytes' parameter to bdrv_padding_rmw_read() Fiona Ebner
2026-01-09 12:08 ` [PATCH 3/6] block/io: honor pwrite_zeroes_alignment in bdrv_co_do_zero_pwritev() Fiona Ebner
2026-01-09 12:08 ` [PATCH 4/6] block/io: safeguard max transfer calculation in bdrv_aligned_pwritev() Fiona Ebner
2026-01-19 19:34   ` Stefan Hajnoczi [this message]
2026-02-05 15:57     ` Kevin Wolf
2026-01-09 12:08 ` [PATCH 5/6] block/io: handle image length not aligned to write zeroes alignment in bdrv_co_do_zero_pwritev() Fiona Ebner
2026-01-09 12:08 ` [PATCH 6/6] block/io: keep zero flag for head/tail parts of misaligned zero write when possible Fiona Ebner
2026-02-02 22:10   ` Stefan Hajnoczi
2026-01-19 19:38 ` [RFC v2 0/6] block/io: avoid failure caused by misaligned BLKZEROOUT ioctl Stefan Hajnoczi
2026-02-02 22:16 ` Stefan Hajnoczi
2026-02-05 12:13   ` Fiona Ebner
2026-02-05 15:26     ` Stefan Hajnoczi
2026-02-05 16:02     ` Kevin Wolf
2026-05-27 21:06       ` Stefan Hajnoczi
2026-05-28  8:32         ` Fiona Ebner
2026-05-28 13:26           ` 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=20260119193452.GC834718@fedora \
    --to=stefanha@redhat.com \
    --cc=f.ebner@proxmox.com \
    --cc=fam@euphon.net \
    --cc=hreitz@redhat.com \
    --cc=kwolf@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.