From: Max Reitz <mreitz@redhat.com>
To: Alberto Garcia <berto@igalia.com>, qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
Markus Armbruster <armbru@redhat.com>,
qemu-block@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 2/3] block: Add 'blockdev-del' QMP command
Date: Sat, 17 Oct 2015 20:23:26 +0200 [thread overview]
Message-ID: <5622921E.40604@redhat.com> (raw)
In-Reply-To: <8dc2b9b2a8c5307eba7fafa2dee8f6e8ef17a26c.1444743418.git.berto@igalia.com>
[-- Attachment #1: Type: text/plain, Size: 2470 bytes --]
On 13.10.2015 15:48, Alberto Garcia wrote:
> This is the companion to 'blockdev-add'. It allows deleting a
> BlockBackend with its associated BlockDriverState tree, or a
> BlockDriverState that is not attached to any backend.
>
> In either case, the command fails if the reference count is greater
> than 1 or the BlockDriverState has any parents.
>
> Signed-off-by: Alberto Garcia <berto@igalia.com>
> ---
> blockdev.c | 42 ++++++++++++++++++++++++++++++++++++++++++
> qapi/block-core.json | 21 +++++++++++++++++++++
> qmp-commands.hx | 36 ++++++++++++++++++++++++++++++++++++
> 3 files changed, 99 insertions(+)
>
> diff --git a/blockdev.c b/blockdev.c
> index 2360c1f..c448a0b 100644
> --- a/blockdev.c
> +++ b/blockdev.c
> @@ -3402,6 +3402,48 @@ fail:
> qmp_output_visitor_cleanup(ov);
> }
>
> +void qmp_blockdev_del(const char *device, Error **errp)
> +{
> + AioContext *aio_context;
> + BlockBackend *blk;
> + BlockDriverState *bs;
> +
> + blk = blk_by_name(device);
> + if (blk) {
> + bs = blk_bs(blk);
> + aio_context = blk_get_aio_context(blk);
> + } else {
> + bs = bdrv_find_node(device);
> + if (!bs) {
> + error_setg(errp, "Cannot find block device %s", device);
> + return;
> + }
> + blk = bs->blk;
After seeing testBlockBackendUsingNodeName() in patch 3, I don't know
about this. We often have this notion of "If you need a BDS, you can
specify both the BB and the node name", but here it's the other way
around: One "needs" a BB (at least that's what the command will work on)
and one gets it by specifying a node name. That seems a bit strange to me.
Max
> + aio_context = bdrv_get_aio_context(bs);
> + }
> +
> + aio_context_acquire(aio_context);
> +
> + if (bs && bdrv_op_is_blocked(bs, BLOCK_OP_TYPE_DRIVE_DEL, errp)) {
> + goto out;
> + }
> +
> + if (blk_get_refcnt(blk) > 1 ||
> + (bs && (bs->refcnt > 1 || !QLIST_EMPTY(&bs->parents)))) {
> + error_setg(errp, "Block device %s is being used", device);
> + goto out;
> + }
> +
> + if (blk) {
> + blk_unref(blk);
> + } else {
> + bdrv_unref(bs);
> + }
> +
> +out:
> + aio_context_release(aio_context);
> +}
> +
> BlockJobInfoList *qmp_query_block_jobs(Error **errp)
> {
> BlockJobInfoList *head = NULL, **p_next = &head;
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2015-10-17 18:23 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-13 13:48 [Qemu-devel] [PATCH 0/3] Add 'blockdev-del' command Alberto Garcia
2015-10-13 13:48 ` [Qemu-devel] [PATCH 1/3] block: Add blk_get_refcnt() Alberto Garcia
2015-10-17 18:06 ` Max Reitz
2015-10-13 13:48 ` [Qemu-devel] [PATCH 2/3] block: Add 'blockdev-del' QMP command Alberto Garcia
2015-10-17 18:06 ` Max Reitz
2015-10-19 14:20 ` Alberto Garcia
2015-10-17 18:23 ` Max Reitz [this message]
2015-10-17 18:32 ` Alberto Garcia
2015-10-13 13:48 ` [Qemu-devel] [PATCH 3/3] iotests: Add test for the blockdev-del command Alberto Garcia
2015-10-19 11:27 ` [Qemu-devel] [PATCH 0/3] Add 'blockdev-del' command Kevin Wolf
2015-10-19 14:15 ` Alberto Garcia
2015-10-19 15:04 ` Kevin Wolf
2015-10-20 15:02 ` Alberto Garcia
2015-10-22 10:38 ` Kevin Wolf
2015-10-22 11:08 ` Alberto Garcia
2015-10-22 11:25 ` Kevin Wolf
2015-10-22 11:31 ` Alberto Garcia
2015-10-22 11:47 ` Kevin Wolf
2015-10-19 14:38 ` Max Reitz
2015-10-21 8:57 ` Markus Armbruster
2015-10-21 9:06 ` Alberto Garcia
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=5622921E.40604@redhat.com \
--to=mreitz@redhat.com \
--cc=armbru@redhat.com \
--cc=berto@igalia.com \
--cc=kwolf@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).