From: Peter Maydell <peter.maydell@linaro.org>
To: Eric Blake <eblake@redhat.com>
Cc: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>,
John Snow <jsnow@redhat.com>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [PULL for 4.2-rc5 0/1] Bitmap fix for 2019-12-09
Date: Mon, 9 Dec 2019 17:12:04 +0000 [thread overview]
Message-ID: <CAFEAcA82rugwnF7zrgtgTfCaZVM9q4Av7hT_Z6Pnw6htMOSb6g@mail.gmail.com> (raw)
In-Reply-To: <20191209160015.20253-1-eblake@redhat.com>
On Mon, 9 Dec 2019 at 16:00, Eric Blake <eblake@redhat.com> wrote:
>
> The following changes since commit 8350b17be015bb872f28268bdeba1bac6c380efc:
>
> Merge remote-tracking branch 'remotes/dgibson/tags/ppc-for-4.2-20191209' into staging (2019-12-09 11:07:34 +0000)
>
> are available in the Git repository at:
>
> https://repo.or.cz/qemu/ericb.git tags/pull-nbd-2019-12-09
>
> for you to fetch changes up to f56281abd957561b30538cbe606c3793b9b4c56d:
>
> block/qcow2-bitmap: fix crash bug in qcow2_co_remove_persistent_dirty_bitmap (2019-12-09 09:23:04 -0600)
>
> [I know I'm not the usual bitmap maintainer, but John agreed that I could
> get this posted faster than he could: it affects incremental bitmaps
> which is tangentially NBD-related, and we're already on a tight timeline
> given this is 4.2-rc5 material]
>
> ----------------------------------------------------------------
> bitmap fix for 4.2-rc5
>
> - Fix a regression that broke bitmap deletion without a transaction,
> and causes a crash with transaction (only transaction is new to 4.2),
> when a qcow2 file contains persistent bitmaps from prior shutdown
>
> ----------------------------------------------------------------
> Vladimir Sementsov-Ogievskiy (1):
> block/qcow2-bitmap: fix crash bug in qcow2_co_remove_persistent_dirty_bitmap
>
> block/qcow2-bitmap.c | 9 ++++++---
> 1 file changed, 6 insertions(+), 3 deletions(-)
Applied, thanks.
Please update the changelog at https://wiki.qemu.org/ChangeLog/4.2
for any user-visible changes.
-- PMM
prev parent reply other threads:[~2019-12-09 17:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-09 16:00 [PULL for 4.2-rc5 0/1] Bitmap fix for 2019-12-09 Eric Blake
2019-12-09 16:00 ` [PULL 1/1] pseries: Update SLOF firmware image Eric Blake
2019-12-09 16:13 ` Eric Blake
2019-12-09 16:13 ` Greg Kurz
2019-12-09 16:16 ` [PATCH for 4.2-rc5 1/1] block/qcow2-bitmap: fix crash bug in qcow2_co_remove_persistent_dirty_bitmap Eric Blake
2019-12-09 17:03 ` John Snow
2019-12-09 22:01 ` Eric Blake
2019-12-09 17:12 ` Peter Maydell [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=CAFEAcA82rugwnF7zrgtgTfCaZVM9q4Av7hT_Z6Pnw6htMOSb6g@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=eblake@redhat.com \
--cc=jsnow@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=vsementsov@virtuozzo.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 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).