qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Max Reitz <mreitz@redhat.com>
To: qemu-block@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>,
	Peter Maydell <peter.maydell@linaro.org>,
	qemu-devel@nongnu.org, Max Reitz <mreitz@redhat.com>
Subject: [PULL 0/2] Block patches for 5.1.0-rc4
Date: Tue, 11 Aug 2020 11:35:03 +0200	[thread overview]
Message-ID: <20200811093505.972894-1-mreitz@redhat.com> (raw)

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.


The following changes since commit e1d322c40524d2c544d1fcd37b267d106d16d328:

  Update version for v5.1.0-rc3 release (2020-08-05 17:37:17 +0100)

are available in the Git repository at:

  https://github.com/XanClic/qemu.git tags/pull-block-2020-08-11

for you to fetch changes up to 1f3765b652930a3b485f1a67542c2410c3774abe:

  iotests: add test for unaligned granularity bitmap backup (2020-08-11 09:29:31 +0200)

----------------------------------------------------------------
Block patches for 5.1.0-rc4:
- Fix abort when running a backup job on an image whose size is not
  aligned to the backup job's cluster size

----------------------------------------------------------------
Stefan Reiter (2):
  block/block-copy: always align copied region to cluster size
  iotests: add test for unaligned granularity bitmap backup

 block/block-copy.c         |  3 ++
 tests/qemu-iotests/304     | 60 ++++++++++++++++++++++++++++++++++++++
 tests/qemu-iotests/304.out |  2 ++
 tests/qemu-iotests/group   |  1 +
 4 files changed, 66 insertions(+)
 create mode 100755 tests/qemu-iotests/304
 create mode 100644 tests/qemu-iotests/304.out

-- 
2.26.2



             reply	other threads:[~2020-08-11  9:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-11  9:35 Max Reitz [this message]
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
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=20200811093505.972894-1-mreitz@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 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).