From: Kevin Wolf <kwolf@redhat.com>
To: Alberto Garcia <berto@igalia.com>
Cc: qemu-devel@nongnu.org, qemu-block@nongnu.org,
Hanna Czenczek <hreitz@redhat.com>,
Andrey Drobyshev <andrey.drobyshev@virtuozzo.com>,
qemu-stable@nongnu.org
Subject: Re: [PATCH] qemu-img rebase: don't exceed IO_BUF_SIZE in one operation
Date: Fri, 7 Nov 2025 13:33:31 +0100 [thread overview]
Message-ID: <aQ3nG4RcLTFaNv6V@redhat.com> (raw)
In-Reply-To: <aQ3mnR1RJiaPau6A@redhat.com>
Am 07.11.2025 um 13:31 hat Kevin Wolf geschrieben:
> Am 07.11.2025 um 10:18 hat Alberto Garcia geschrieben:
> > During a rebase operation data is copied from the backing chain into
> > the target image using a loop, and each iteration looks for a
> > contiguous region of allocated data of at most IO_BUF_SIZE (2 MB).
> >
> > Once that region is found, and in order to avoid partial writes, its
> > boundaries are extended so they are aligned to the (sub)clusters of
> > the target image (see commit 12df580b).
> >
> > This operation can however result in a region that exceeds the maximum
> > allowed IO_BUF_SIZE, crashing qemu-img.
> >
> > This can be easily reproduced when the source image has a smaller
> > cluster size than the target image:
> >
> > base <- int <- active
> >
> > $ qemu-img create -f qcow2 base.qcow2 4M
> > $ qemu-img create -f qcow2 -F qcow2 -b base.qcow2 -o cluster_size=1M int.qcow2
> > $ qemu-img create -f qcow2 -F qcow2 -b int.qcow2 -o cluster_size=2M active.qcow2
> > $ qemu-io -c "write -P 0xff 1M 2M" int.qcow2
> > $ qemu-img rebase -F qcow2 -b base.qcow2 active.qcow2
> > qemu-img: qemu-img.c:4102: img_rebase: Assertion `written + pnum <= IO_BUF_SIZE' failed.
> > Aborted
> >
> > Resolves: https://gitlab.com/qemu-project/qemu/-/issues/3174
> > Fixes: 12df580b3b7f ("qemu-img: rebase: avoid unnecessary COW operations")
> > Signed-off-by: Alberto Garcia <berto@igalia.com>
Oops, I forgot to mention the other point I had:
Cc: qemu-stable <qemu-stable@nongnu.org>
Added it to the Cc: list of this reply and also to the commit message.
Kevin
prev parent reply other threads:[~2025-11-07 12:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-07 9:18 [PATCH] qemu-img rebase: don't exceed IO_BUF_SIZE in one operation Alberto Garcia
2025-11-07 12:31 ` Kevin Wolf
2025-11-07 12:33 ` Kevin Wolf [this message]
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=aQ3nG4RcLTFaNv6V@redhat.com \
--to=kwolf@redhat.com \
--cc=andrey.drobyshev@virtuozzo.com \
--cc=berto@igalia.com \
--cc=hreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).