All of lore.kernel.org
 help / color / mirror / Atom feed
From: Max Reitz <mreitz@redhat.com>
To: Wenchao Xia <xiawenc@linux.vnet.ibm.com>, qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>,
	Paolo Bonzini <pbonzini@redhat.com>, Fam Zheng <famz@redhat.com>,
	Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v3 0/2] block/drive-mirror: Check for NULL backing_hd
Date: Thu, 07 Nov 2013 10:11:49 +0100	[thread overview]
Message-ID: <527B5955.6020303@redhat.com> (raw)
In-Reply-To: <527AFA03.8040402@linux.vnet.ibm.com>

On 07.11.2013 03:25, Wenchao Xia wrote:
> 于 2013/11/7 2:50, Max Reitz 写道:
>> 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.
>>
>> v2:
>>   - patch 1: Reuse an already existing codepath to create an unbacked
>>              target image instead of introducing a new one (based on
>>              Fam's comment).
>>   - patch 2: Incorporated test case into 041 instead of creating a new
>>              file (according to Xia's and Paolo's comments).
>>
>>
>> Max Reitz (2):
>>    block/drive-mirror: Check for NULL backing_hd
>>    qemu-iotests: Extend 041 for unbacked mirroring
>>
>>   blockdev.c                 |  4 +++-
>>   tests/qemu-iotests/041     | 25 +++++++++++++++++++++++++
>>   tests/qemu-iotests/041.out |  4 ++--
>>   3 files changed, 30 insertions(+), 3 deletions(-)
>>
> Reviewed-by: Wenchao Xia <xiawenc@linux.vnet.ibm.com>
>
> Should we change doc for NewImageMode in qapi-schema.json also?

Probably, yes. I'll send a follow-up patch.

Max

  reply	other threads:[~2013-11-07  9:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-06 18:50 [Qemu-devel] [PATCH v3 0/2] block/drive-mirror: Check for NULL backing_hd Max Reitz
2013-11-06 18:50 ` [Qemu-devel] [PATCH v3 1/2] " Max Reitz
2013-11-06 19:01   ` Eric Blake
2013-11-06 18:50 ` [Qemu-devel] [PATCH v3 2/2] qemu-iotests: Extend 041 for unbacked mirroring Max Reitz
2013-11-07  9:51   ` Paolo Bonzini
2013-11-07  2:25 ` [Qemu-devel] [PATCH v3 0/2] block/drive-mirror: Check for NULL backing_hd Wenchao Xia
2013-11-07  9:11   ` Max Reitz [this message]
2013-11-11 16:05 ` Kevin Wolf

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=527B5955.6020303@redhat.com \
    --to=mreitz@redhat.com \
    --cc=famz@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    --cc=xiawenc@linux.vnet.ibm.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.