From: Alberto Garcia <berto@igalia.com>
To: qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>, Alberto Garcia <berto@igalia.com>,
qemu-block@nongnu.org, Markus Armbruster <armbru@redhat.com>,
Max Reitz <mreitz@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>
Subject: [Qemu-devel] [PATCH 0/2] Don't allow snapshots if the overlay has parent nodes
Date: Thu, 29 Oct 2015 15:00:47 +0200 [thread overview]
Message-ID: <cover.1446123576.git.berto@igalia.com> (raw)
There are several sanity checks for the 'blockdev-snapshot' command,
but none covers the use of a file BDS as the overlay node.
{ 'execute': 'blockdev-add', 'arguments':
{ 'options': { 'driver': 'qcow2',
'node-name': 'new0',
'file': { 'driver': 'file',
'filename': 'new.qcow2',
'node-name': 'file0' } } } }
{ 'execute': 'blockdev-snapshot', 'arguments':
{ 'node': 'virtio0',
'overlay': 'file0' } }
This series fixes that and adds a new test case. This of course
depends on the 'blockdev-snapshot' series:
https://lists.gnu.org/archive/html/qemu-block/2015-10/msg00974.html
I anyway wonder if it wouldn't be a good idea to have regular op
blockers in all file BDSs?
Regards,
Berto
Alberto Garcia (2):
block: Don't allow snapshots if the overlay has parent nodes
block: test 'blockdev-snapshot' using a file BDS as the overlay
blockdev.c | 5 +++++
tests/qemu-iotests/085 | 12 +++++++++++-
tests/qemu-iotests/085.out | 4 ++++
3 files changed, 20 insertions(+), 1 deletion(-)
--
2.6.1
next reply other threads:[~2015-10-29 13:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-29 13:00 Alberto Garcia [this message]
2015-10-29 13:00 ` [Qemu-devel] [PATCH 1/2] block: Don't allow snapshots if the overlay has parent nodes Alberto Garcia
2015-10-29 13:00 ` [Qemu-devel] [PATCH 2/2] block: test 'blockdev-snapshot' using a file BDS as the overlay Alberto Garcia
2015-10-30 18:22 ` [Qemu-devel] [PATCH 0/2] Don't allow snapshots if the overlay has parent nodes 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=cover.1446123576.git.berto@igalia.com \
--to=berto@igalia.com \
--cc=armbru@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.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 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.