qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Fam Zheng <famz@redhat.com>
To: Alberto Garcia <berto@igalia.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
	Stefan Hajnoczi <stefanha@redhat.com>,
	qemu-devel@nongnu.org, qemu-block@nongnu.org,
	Max Reitz <mreitz@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v4 2/4] block: support passing 'backing': '' to 'blockdev-add'
Date: Tue, 15 Sep 2015 10:27:21 +0800	[thread overview]
Message-ID: <20150915022721.GE14016@ad.nay.redhat.com> (raw)
In-Reply-To: <fac86ccf2408b4f417eb744e56edd906b2c0d86b.1442245236.git.berto@igalia.com>

On Mon, 09/14 19:01, Alberto Garcia wrote:
> Passing an empty string allows opening an image but not its backing
> file. This was already described in the API documentation, only the
> implementation was missing.
> 
> This is useful for creating snapshots using images opened with
> blockdev-add, since they are not supposed to have a backing image
> before the operation.
> 
> Signed-off-by: Alberto Garcia <berto@igalia.com>
> ---
>  block.c | 7 +++++++
>  1 file changed, 7 insertions(+)
> 
> diff --git a/block.c b/block.c
> index 22d3b0e..ad1792d 100644
> --- a/block.c
> +++ b/block.c
> @@ -1402,6 +1402,7 @@ static int bdrv_open_inherit(BlockDriverState **pbs, const char *filename,
>      BlockDriverState *file = NULL, *bs;
>      BlockDriver *drv = NULL;
>      const char *drvname;
> +    const char *backing;
>      Error *local_err = NULL;
>      int snapshot_flags = 0;
>  
> @@ -1469,6 +1470,12 @@ static int bdrv_open_inherit(BlockDriverState **pbs, const char *filename,
>  
>      assert(drvname || !(flags & BDRV_O_PROTOCOL));
>  
> +    backing = qdict_get_try_str(options, "backing");
> +    if (backing && *backing == '\0') {
> +        flags |= BDRV_O_NO_BACKING;
> +    }
> +    qdict_del(options, "backing");
> +
>      bs->open_flags = flags;
>      bs->options = options;
>      options = qdict_clone_shallow(options);
> -- 
> 2.5.1
> 
> 

Specifying a non-empty "backing" will be a slient nop now, but it used to be an
error before.  Should we return an error?

Fam

  reply	other threads:[~2015-09-15  2:27 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-14 16:01 [Qemu-devel] [PATCH v4 0/4] Add 'blockdev-snapshot' command Alberto Garcia
2015-09-14 16:01 ` [Qemu-devel] [PATCH v4 1/4] block: rename BlockdevSnapshot to BlockdevSnapshotSync Alberto Garcia
2015-09-18 10:35   ` Max Reitz
2015-09-14 16:01 ` [Qemu-devel] [PATCH v4 2/4] block: support passing 'backing': '' to 'blockdev-add' Alberto Garcia
2015-09-15  2:27   ` Fam Zheng [this message]
2015-09-15  6:42     ` Alberto Garcia
2015-09-18 14:41       ` Eric Blake
2015-09-14 16:01 ` [Qemu-devel] [PATCH v4 3/4] block: add a 'blockdev-snapshot' QMP command Alberto Garcia
2015-09-18 10:44   ` Max Reitz
2015-09-18 14:49   ` Eric Blake
2015-09-22  9:21     ` Alberto Garcia
2015-09-22  9:32       ` Kevin Wolf
2015-09-14 16:01 ` [Qemu-devel] [PATCH v4 4/4] block: add tests for the 'blockdev-snapshot' command Alberto Garcia
2015-09-18 10:49   ` 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=20150915022721.GE14016@ad.nay.redhat.com \
    --to=famz@redhat.com \
    --cc=berto@igalia.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 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).