From: Stefan Hajnoczi <stefanha@redhat.com>
To: Fam Zheng <famz@redhat.com>
Cc: kwolf@redhat.com, obarenbo@redhat.com, armbru@redhat.com,
roliveri@redhat.com, hbrock@redhat.com, qemu-devel@nongnu.org,
rjones@redhat.com, pmyers@redhat.com, imain@redhat.com,
pbonzini@redhat.com
Subject: Re: [Qemu-devel] [RFC PATCH 1/3] block: add target-id option to drive-backup QMP command
Date: Thu, 27 Jun 2013 10:15:36 +0200 [thread overview]
Message-ID: <20130627081536.GE13780@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <1372219161-12209-2-git-send-email-famz@redhat.com>
On Wed, Jun 26, 2013 at 11:59:19AM +0800, Fam Zheng wrote:
> Add target-id (optional) to drive-backup command, to make the target bs
> a named drive so that we can operate on it (e.g. export with NBD).
>
> Signed-off-by: Fam Zheng <famz@redhat.com>
> ---
> blockdev.c | 4 +++-
> qapi-schema.json | 7 +++++--
> qmp-commands.hx | 3 ++-
> 3 files changed, 10 insertions(+), 4 deletions(-)
>
> diff --git a/blockdev.c b/blockdev.c
> index b3a57e0..5e694f3 100644
> --- a/blockdev.c
> +++ b/blockdev.c
> @@ -935,6 +935,7 @@ static void drive_backup_prepare(BlkTransactionState *common, Error **errp)
> backup = common->action->drive_backup;
>
> qmp_drive_backup(backup->device, backup->target,
> + backup->has_target_id, backup->target_id,
> backup->has_format, backup->format,
> backup->has_mode, backup->mode,
> backup->has_speed, backup->speed,
> @@ -1420,6 +1421,7 @@ void qmp_block_commit(const char *device,
> }
>
> void qmp_drive_backup(const char *device, const char *target,
> + bool has_target_id, const char *target_id,
> bool has_format, const char *format,
> bool has_mode, enum NewImageMode mode,
> bool has_speed, int64_t speed,
> @@ -1494,7 +1496,7 @@ void qmp_drive_backup(const char *device, const char *target,
> return;
> }
>
> - target_bs = bdrv_new("");
> + target_bs = bdrv_new(has_target_id ? target_id : "");
This raises a new issue:
Now that the target can be named, what happens when the user issues a
monitor command, e.g. drive-del, block-resize, or drive-backup :)?
We have a clumsy form of protection with bdrv_set_in_use(). It makes
several monitor commands refuse with -EBUSY.
Perhaps we should have a command permission set so it's possible to
allow/deny specific commands.
Stefan
next prev parent reply other threads:[~2013-06-27 8:15 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-26 3:59 [Qemu-devel] [RFC PATCH 0/3] Point-in-time snapshot exporting with drive-backup Fam Zheng
2013-06-26 3:59 ` [Qemu-devel] [RFC PATCH 1/3] block: add target-id option to drive-backup QMP command Fam Zheng
2013-06-27 8:15 ` Stefan Hajnoczi [this message]
2013-06-27 9:41 ` Fam Zheng
2013-06-27 10:57 ` Paolo Bonzini
2013-06-27 11:37 ` Fam Zheng
2013-06-27 11:40 ` Paolo Bonzini
2013-06-28 2:17 ` Fam Zheng
2013-06-26 3:59 ` [Qemu-devel] [RFC PATCH 2/3] block: assign backing relationship in drive-backup Fam Zheng
2013-06-26 7:15 ` Paolo Bonzini
2013-06-26 3:59 ` [Qemu-devel] [RFC PATCH 3/3] nbd: don't get ref if bs has no drive Fam Zheng
2013-06-26 7:23 ` [Qemu-devel] [RFC PATCH 0/3] Point-in-time snapshot exporting with drive-backup Paolo Bonzini
2013-06-26 7:31 ` Fam Zheng
2013-06-27 8:17 ` Stefan Hajnoczi
2013-06-27 10:06 ` Paolo Bonzini
2013-06-27 13:39 ` Stefan Hajnoczi
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=20130627081536.GE13780@stefanha-thinkpad.redhat.com \
--to=stefanha@redhat.com \
--cc=armbru@redhat.com \
--cc=famz@redhat.com \
--cc=hbrock@redhat.com \
--cc=imain@redhat.com \
--cc=kwolf@redhat.com \
--cc=obarenbo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=pmyers@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rjones@redhat.com \
--cc=roliveri@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).