From: Paolo Bonzini <pbonzini@redhat.com>
To: Max Reitz <mreitz@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
qemu-devel@nongnu.org, Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v2 0/2] block/drive-mirror: Check for NULL backing_hd
Date: Tue, 05 Nov 2013 11:53:21 +0100 [thread overview]
Message-ID: <5278CE21.5030204@redhat.com> (raw)
In-Reply-To: <1383611706-22107-1-git-send-email-mreitz@redhat.com>
Il 05/11/2013 01:35, Max Reitz ha scritto:
> It should be possible to execute the QMP "drive-mirror" command in
> "none" sync mode and "absolute-paths" mode even for block devices
> lacking a backing file.
>
> "absolute-paths" does in fact not require a backing file to be present,
> as can be seen from the "top" sync mode code path. "top" basically
> states that the device should indeed have a backing file - however, the
> current code catches the case if it doesn't and then simply treats it as
> "full" sync mode, creating a target image without a backing file (in
> "absolute-paths" mode). Thus, "absolute-paths" does not imply the target
> file must indeed have a backing file.
>
> Therefore, the target file may be left unbacked in case of "none" sync
> mode as well, if the specified device is not backed either. Currently,
> qemu will crash trying to dereference the backing file pointer since it
> assumes that it will always be non-NULL in that case ("none" with
> "absolute-paths").
>
> The first patch in this series adds a check whether the specified block
> device is backed or not (creating an unbacked target image, if required);
> the second patch adds a test case for mirroring unbacked block devices.
>
>
> Max Reitz (2):
> block/drive-mirror: Check for NULL backing_hd
> qemu-iotests: Add test for unbacked mirroring
>
> blockdev.c | 4 +-
> tests/qemu-iotests/070 | 91 ++++++++++++++++++++++++++++++++++++++++++++++
> tests/qemu-iotests/070.out | 33 +++++++++++++++++
> tests/qemu-iotests/group | 1 +
> 4 files changed, 127 insertions(+), 2 deletions(-)
> create mode 100755 tests/qemu-iotests/070
> create mode 100644 tests/qemu-iotests/070.out
>
Patch 1 is fine.
For patch 2, there are existing drive-mirror tests written in Python.
I'll let the maintainers whether they are fine with a new test, or
prefer to extend those with a new testcase.
Paolo
prev parent reply other threads:[~2013-11-05 10:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-05 0:35 [Qemu-devel] [PATCH v2 0/2] block/drive-mirror: Check for NULL backing_hd Max Reitz
2013-11-05 0:35 ` [Qemu-devel] [PATCH v2 1/2] " Max Reitz
2013-11-05 3:32 ` Fam Zheng
2013-11-05 19:06 ` Max Reitz
2013-11-05 0:35 ` [Qemu-devel] [PATCH v2 2/2] qemu-iotests: Add test for unbacked mirroring Max Reitz
2013-11-05 9:00 ` Wenchao Xia
2013-11-05 19:08 ` Max Reitz
2013-11-05 10:53 ` Paolo Bonzini [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=5278CE21.5030204@redhat.com \
--to=pbonzini@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--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.