From: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
To: qemu-block@nongnu.org
Cc: kwolf@redhat.com, vsementsov@virtuozzo.com,
qemu-devel@nongnu.org, mreitz@redhat.com, den@openvz.org,
jsnow@redhat.com
Subject: [PATCH v2 0/2] fix qcow2_can_store_new_dirty_bitmap
Date: Mon, 14 Oct 2019 14:51:24 +0300 [thread overview]
Message-ID: <20191014115126.15360-1-vsementsov@virtuozzo.com> (raw)
Hi all!
Here is a fix for persistent bitmaps managing: we must check existent
but not yet stored bitmaps for qcow2-related constraints, like maximum
number of bitmaps in qcow2 image.
v2:
01: change assertion to error-return at function start
Be free to add
Reported-by: aihua liang <aliang@redhat.com>
Fixes: https://bugzilla.redhat.com/show_bug.cgi?id=1712636
if it's appropriate
02: new test
Ohh, it takes about 4 minutes. Be free to drop it, as I doubt that
it worth to have. The case is simple, we may live without a
test.
Vladimir Sementsov-Ogievskiy (2):
qcow2-bitmaps: fix qcow2_can_store_new_dirty_bitmap
iotests: add 269 to check maximum of bitmaps in qcow2
block/qcow2-bitmap.c | 41 +++++++++++++++------------------
tests/qemu-iotests/269 | 47 ++++++++++++++++++++++++++++++++++++++
tests/qemu-iotests/269.out | 3 +++
tests/qemu-iotests/group | 1 +
4 files changed, 69 insertions(+), 23 deletions(-)
create mode 100755 tests/qemu-iotests/269
create mode 100644 tests/qemu-iotests/269.out
--
2.21.0
next reply other threads:[~2019-10-14 11:57 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-14 11:51 Vladimir Sementsov-Ogievskiy [this message]
2019-10-14 11:51 ` [PATCH v2 1/2] qcow2-bitmaps: fix qcow2_can_store_new_dirty_bitmap Vladimir Sementsov-Ogievskiy
2019-10-25 12:50 ` Max Reitz
2019-10-25 12:56 ` Vladimir Sementsov-Ogievskiy
2019-12-09 16:32 ` Max Reitz
2019-10-14 11:51 ` [PATCH v2 2/2] iotests: add 269 to check maximum of bitmaps in qcow2 Vladimir Sementsov-Ogievskiy
2019-10-25 13:12 ` Max Reitz
2019-11-16 9:41 ` Vladimir Sementsov-Ogievskiy
2019-10-14 11:52 ` [PATCH v2 0/2] fix qcow2_can_store_new_dirty_bitmap Vladimir Sementsov-Ogievskiy
2019-10-25 9:57 ` [bugfix ping] " Vladimir Sementsov-Ogievskiy
2019-12-02 14:09 ` [bugfix ping2] " Vladimir Sementsov-Ogievskiy
2019-12-09 16:30 ` Max Reitz
2019-12-09 17:58 ` Max Reitz
2019-12-09 22:03 ` Eric Blake
2019-12-10 8:11 ` Max Reitz
2019-12-10 13:24 ` Max Reitz
2019-12-10 20:27 ` John Snow
2019-12-11 8:10 ` Vladimir Sementsov-Ogievskiy
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=20191014115126.15360-1-vsementsov@virtuozzo.com \
--to=vsementsov@virtuozzo.com \
--cc=den@openvz.org \
--cc=jsnow@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--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).