From: Alberto Garcia <berto@igalia.com>
To: Max Reitz <mreitz@redhat.com>, Kevin Wolf <kwolf@redhat.com>
Cc: Qemu-block <qemu-block@nongnu.org>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Markus Armbruster <armbru@redhat.com>,
"Denis V. Lunev" <den@openvz.org>,
Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
Subject: Re: [Qemu-devel] KVM Forum block no[td]es
Date: Fri, 16 Nov 2018 18:16:27 +0100 [thread overview]
Message-ID: <w51d0r554es.fsf@maestria.local.igalia.com> (raw)
In-Reply-To: <1d65ed3f-7353-002f-9000-3b824d5892ce@redhat.com>
(I just wanted to reply quickly to this point, I'll read the rest of the
e-mail later)
On Fri 16 Nov 2018 05:34:08 PM CET, Max Reitz <mreitz@redhat.com> wrote:
> > GRAPH_MOD with the meaning that Berto suggested isn't weird or
> > complicated to understand. It's only the wrong tool because it
> > blocks more than we want to block. But if we didn't care about that,
> > it could be just another permission like any other.
That's the way that I understood it. Or, more precisely, I'm basing my
current code on those assumptions because it's a simple starting point
to have something working with the current permission system. But I'm of
course open to trying a different approach.
> The meaning Berto has suggested (AFAIU) is never taking the permission
> at all but just querying whether it is shared by all current parents
> before doing a graph change.
That would be a quick way to test it, and I agree that it's unorthodox,
but it's useful to explain how I understood the meaning of GRAPH_MOD.
But you could for example make BDRVReopenState a parent of the BDS (and
replace BDRVReopenState.bs with a BdrvChild).
Berto
next prev parent reply other threads:[~2018-11-16 17:16 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-11 22:25 [Qemu-devel] KVM Forum block no[td]es Max Reitz
2018-11-11 23:36 ` [Qemu-devel] [Qemu-block] " Nir Soffer
2018-11-12 15:25 ` Max Reitz
2018-11-12 16:10 ` Nir Soffer
2018-11-21 1:24 ` Vladimir Sementsov-Ogievskiy
2018-11-14 19:38 ` John Snow
2018-11-13 15:12 ` [Qemu-devel] " Alberto Garcia
2018-11-14 17:24 ` Max Reitz
2018-11-15 14:28 ` Alberto Garcia
2018-11-16 12:14 ` Max Reitz
2018-11-16 15:03 ` Alberto Garcia
2018-11-16 15:18 ` Kevin Wolf
2018-11-16 15:27 ` Max Reitz
2018-11-16 15:51 ` Kevin Wolf
2018-11-16 16:34 ` Max Reitz
2018-11-16 17:13 ` Kevin Wolf
2018-11-16 18:23 ` Max Reitz
2018-11-16 17:16 ` Alberto Garcia [this message]
2018-11-19 16:47 ` Alberto Garcia
2018-11-16 15:19 ` Max Reitz
2018-11-16 15:20 ` Alberto Garcia
2018-11-16 7:47 ` Denis V.Lunev
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=w51d0r554es.fsf@maestria.local.igalia.com \
--to=berto@igalia.com \
--cc=armbru@redhat.com \
--cc=den@openvz.org \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=vsementsov@virtuozzo.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.