qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Andrey Drobyshev <andrey.drobyshev@virtuozzo.com>
To: Michael Tokarev <mjt@tls.msk.ru>, qemu-block@nongnu.org
Cc: qemu-devel@nongnu.org, hreitz@redhat.com, kwolf@redhat.com,
	eblake@redhat.com, den@virtuozzo.com
Subject: Re: [PATCH v3 1/8] qemu-img: rebase: stop when reaching EOF of old backing file
Date: Wed, 1 Nov 2023 17:38:20 +0200	[thread overview]
Message-ID: <676efe0e-0c13-433b-9ca5-18c14920050d@virtuozzo.com> (raw)
In-Reply-To: <b19cfb5c-658f-4bf2-a872-7eaa252d68b4@tls.msk.ru>

On 11/1/23 11:50, Michael Tokarev wrote:
> 19.09.2023 19:57, Andrey Drobyshev via wrote:
>> In case when we're rebasing within one backing chain, and when target
>> image
>> is larger than old backing file, bdrv_is_allocated_above() ends up
>> setting
>> *pnum = 0.  As a result, target offset isn't getting incremented, and we
>> get stuck in an infinite for loop.  Let's detect this case and proceed
>> further down the loop body, as the offsets beyond the old backing size
>> need
>> to be explicitly zeroed.
>>
>> Signed-off-by: Andrey Drobyshev <andrey.drobyshev@virtuozzo.com>
>> Reviewed-by: Denis V. Lunev <den@openvz.org>
>> Reviewed-by: Hanna Czenczek <hreitz@redhat.com>
> 
> Is this change not for -stable anymore?  First version of this patch has
> been
> Cc'd to stable, this one is not.
> 
> Thanks,
> 
> /mjt

Hi Michael,

Since this series is already merged in master, I'm not sure whether it's
necessary to forward this particular patch to qemu-stable, or it should
rather be cherry-picked to -stable by one of the block maintainers.

Kevin, maybe you can clarify?

Andrey


  reply	other threads:[~2023-11-01 15:38 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-19 16:57 [PATCH v3 0/8] qemu-img: rebase: add compression support Andrey Drobyshev via
2023-09-19 16:57 ` [PATCH v3 1/8] qemu-img: rebase: stop when reaching EOF of old backing file Andrey Drobyshev via
2023-11-01  9:50   ` Michael Tokarev
2023-11-01 15:38     ` Andrey Drobyshev [this message]
2023-11-01 17:51       ` Michael Tokarev
2023-11-02 10:46         ` Kevin Wolf
2023-09-19 16:57 ` [PATCH v3 2/8] qemu-iotests: 024: add rebasing test case for overlay_size > backing_size Andrey Drobyshev via
2023-09-19 16:57 ` [PATCH v3 3/8] qemu-img: rebase: use backing files' BlockBackend for buffer alignment Andrey Drobyshev via
2023-09-19 16:58 ` [PATCH v3 4/8] qemu-img: add chunk size parameter to compare_buffers() Andrey Drobyshev via
2023-10-17 19:30   ` Kevin Wolf
2023-09-19 16:58 ` [PATCH v3 5/8] qemu-img: rebase: avoid unnecessary COW operations Andrey Drobyshev via
2023-09-19 16:58 ` [PATCH v3 6/8] iotests/{024, 271}: add testcases for qemu-img rebase Andrey Drobyshev via
2023-09-19 16:58 ` [PATCH v3 7/8] qemu-img: add compression option to rebase subcommand Andrey Drobyshev via
2023-09-19 16:58 ` [PATCH v3 8/8] iotests: add tests for "qemu-img rebase" with compression Andrey Drobyshev via
2023-10-02  6:35 ` [PATCH v3 0/8] qemu-img: rebase: add compression support Andrey Drobyshev
2023-10-16  8:34   ` Andrey Drobyshev
2023-10-17 20:08 ` Kevin Wolf

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=676efe0e-0c13-433b-9ca5-18c14920050d@virtuozzo.com \
    --to=andrey.drobyshev@virtuozzo.com \
    --cc=den@virtuozzo.com \
    --cc=eblake@redhat.com \
    --cc=hreitz@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=mjt@tls.msk.ru \
    --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 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).