From: Max Reitz <mreitz@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Kevin Wolf <kwolf@redhat.com>,
QEMU Developers <qemu-devel@nongnu.org>,
Qemu-block <qemu-block@nongnu.org>
Subject: Re: [PULL 0/2] Block patches for 5.1.0-rc4
Date: Tue, 11 Aug 2020 11:54:59 +0200 [thread overview]
Message-ID: <615bc8ec-d686-cdd7-88aa-8023c26d6c69@redhat.com> (raw)
In-Reply-To: <CAFEAcA_v=pTcao6-42bQP7yhVq1Zinjk-bbE71Bksu0=LaON0A@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 880 bytes --]
On 11.08.20 11:39, Peter Maydell wrote:
> On Tue, 11 Aug 2020 at 10:35, Max Reitz <mreitz@redhat.com> wrote:
>>
>> Hi,
>>
>> There is a bug in the backup job that breaks backups from images whose
>> size is not aligned to the job's cluster size (i.e., qemu crashes
>> because of a failed assertion). If this bug makes it into the release,
>> it would be a regression from 5.0.
>>
>> On one hand, this is probably a rare configuration that should not
>> happen in practice. On the other, it is a regression, and the fix
>> (patch 1) is simple. So I think it would be good to have this in 5.1.
>
> I'm really reluctant to have to roll an rc4...
Well, that’s the information there is on this: Regression, simple fix,
but little relevance in practice, and late to the party.
If, given this, you don’t want to roll an rc4, then that’s how it is.
Max
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-08-11 9:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-11 9:35 [PULL 0/2] Block patches for 5.1.0-rc4 Max Reitz
2020-08-11 9:35 ` [PULL 1/2] block/block-copy: always align copied region to cluster size Max Reitz
2020-08-11 9:35 ` [PULL 2/2] iotests: add test for unaligned granularity bitmap backup Max Reitz
2020-08-11 9:39 ` [PULL 0/2] Block patches for 5.1.0-rc4 Peter Maydell
2020-08-11 9:54 ` Max Reitz [this message]
2021-05-28 12:12 ` Vladimir Sementsov-Ogievskiy
2020-08-20 8:45 ` Peter Maydell
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=615bc8ec-d686-cdd7-88aa-8023c26d6c69@redhat.com \
--to=mreitz@redhat.com \
--cc=kwolf@redhat.com \
--cc=peter.maydell@linaro.org \
--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.