From: Max Reitz <mreitz@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>, Alberto Garcia <berto@igalia.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 16:27:20 +0100 [thread overview]
Message-ID: <001ec125-35f3-e1fb-56a7-1ed4a1974cc6@redhat.com> (raw)
In-Reply-To: <20181116151834.GA5066@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 1341 bytes --]
On 16.11.18 16:18, Kevin Wolf wrote:
> Am 16.11.2018 um 16:03 hat Alberto Garcia geschrieben:
>>> I don't think anything needs a way to generally block graph changes
>>> around some node. We only need to prevent changes to very specific
>>> sets of edges. This is something that the permission system just
>>> cannot do.
>>
>> But what would you do then?
>
> I agree with you mostly in that I think that most problems that Max
> mentioned aren't readl. The only real problem I see with GRAPH_MOD as a
> permission on the node level is this overblocking
I wholeheartedly disagree. Yes, it is true that most of the issues I
thought of can be fixed, and so those problems are not problems in a
technical sense. But to me this whole discussion points to the greatest
issue I have, which is that GRAPH_MOD is just too complicated to
understand. And I don't like a solution that works on a technical level
but that everybody is too afraid to touch because it's too weird.
We have this discussion again and again, and in the end we always come
up with something that looks like it might work, but it's just so weird
that we can't even remember it.
Maybe it's just me, though. Frankly, I think the permission system
itself is already too complicated as it is, but I don't have a simpler
solution there.
Max
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2018-11-16 15:27 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 [this message]
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
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=001ec125-35f3-e1fb-56a7-1ed4a1974cc6@redhat.com \
--to=mreitz@redhat.com \
--cc=armbru@redhat.com \
--cc=berto@igalia.com \
--cc=den@openvz.org \
--cc=kwolf@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 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).