qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Alberto Garcia <berto@igalia.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: qemu-devel@nongnu.org, qemu-block@nongnu.org,
	Max Reitz <mreitz@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v2 1/2] block: Allow x-blockdev-del on a BB with a monitor-owned BDS
Date: Fri, 26 Feb 2016 10:09:56 +0100	[thread overview]
Message-ID: <w51y4a7on17.fsf@maestria.local.igalia.com> (raw)
In-Reply-To: <20160226085854.GA5668@noname.redhat.com>

On Fri 26 Feb 2016 09:58:54 AM CET, Kevin Wolf wrote:
>> I think your case is reasonable, but it's not the only way to get
>> into this situation. See for example this one:
>> 
>> blockdev-add 'drive0', 'node0'
>> blockdev-add 'node1'
>> blockdev-snapshot node='node0' overlay='node1'
>> 
>> Now you have 'drive0' with 'node0' <- 'node1'.
>> 
>> You cannot simply remove 'drive0', you need to eject 'node1' first
>> and then you can remove 'drive0' and 'node1'.
>
> I think this is even more a reason not to introduce any magic but to
> require that node and BB be removed separately. Otherwise it will
> become really confusing to track for management software which node is
> supposed to automatically go away and which isn't.

Note that with this patch you still need to remove the node and the BB
separately, it only spares you to eject a node that was not explicitly
inserted in the first place.

That said, I think Max's example convinced me that this is not as clear
as I initially thought, so if you're not convinced either I have no
problem to withdraw the patch.

Thanks,

Berto

  reply	other threads:[~2016-02-26  9:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-09 15:57 [Qemu-devel] [PATCH v2 0/2] Allow x-blockdev-del on a BB with a monitor-owned BDS Alberto Garcia
2016-02-09 15:57 ` [Qemu-devel] [PATCH v2 1/2] block: " Alberto Garcia
2016-02-24 16:15   ` Max Reitz
2016-02-25 11:11     ` Alberto Garcia
2016-02-26  8:58       ` Kevin Wolf
2016-02-26  9:09         ` Alberto Garcia [this message]
2016-02-09 15:57 ` [Qemu-devel] [PATCH v2 2/2] block: Update the x-blockdev-del documentation Alberto Garcia
2016-02-24 12:51 ` [Qemu-devel] [PATCH v2 0/2] Allow x-blockdev-del on a BB with a monitor-owned BDS 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=w51y4a7on17.fsf@maestria.local.igalia.com \
    --to=berto@igalia.com \
    --cc=kwolf@redhat.com \
    --cc=mreitz@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    /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).