From: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
To: qemu-block@nongnu.org
Cc: kwolf@redhat.com, qemu-stable@nongnu.org,
vsementsov@virtuozzo.com, qemu-devel@nongnu.org,
mreitz@redhat.com
Subject: [PATCH 0/2] backup-top failure path fix
Date: Thu, 16 Jan 2020 18:54:50 +0300 [thread overview]
Message-ID: <20200116155452.30972-1-vsementsov@virtuozzo.com> (raw)
Hi all!
Here is a small crash fix.
Vladimir Sementsov-Ogievskiy (2):
block/backup-top: fix failure path
iotests: add test for backup-top failure on permission activation
block/backup-top.c | 21 ++++++-----
tests/qemu-iotests/283 | 75 ++++++++++++++++++++++++++++++++++++++
tests/qemu-iotests/283.out | 8 ++++
tests/qemu-iotests/group | 1 +
4 files changed, 96 insertions(+), 9 deletions(-)
create mode 100644 tests/qemu-iotests/283
create mode 100644 tests/qemu-iotests/283.out
--
2.21.0
next reply other threads:[~2020-01-16 15:56 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-16 15:54 Vladimir Sementsov-Ogievskiy [this message]
2020-01-16 15:54 ` [PATCH 1/2] block/backup-top: fix failure path Vladimir Sementsov-Ogievskiy
2020-01-20 16:50 ` Max Reitz
2020-01-16 15:54 ` [PATCH 2/2] iotests: add test for backup-top failure on permission activation Vladimir Sementsov-Ogievskiy
2020-01-20 17:04 ` Max Reitz
2020-01-20 17:20 ` Vladimir Sementsov-Ogievskiy
2020-01-21 9:14 ` Max Reitz
2020-01-21 9:23 ` Vladimir Sementsov-Ogievskiy
2020-01-21 9:41 ` Max Reitz
2020-01-21 10:40 ` Vladimir Sementsov-Ogievskiy
2020-01-21 12:39 ` Max Reitz
2020-01-21 12:53 ` Vladimir Sementsov-Ogievskiy
2020-01-21 13:29 ` Max Reitz
2020-01-21 13:48 ` Vladimir Sementsov-Ogievskiy
2020-01-21 13:51 ` Max Reitz
2020-01-21 13:55 ` Vladimir Sementsov-Ogievskiy
2020-01-21 14:01 ` Max Reitz
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=20200116155452.30972-1-vsementsov@virtuozzo.com \
--to=vsementsov@virtuozzo.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@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).