qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Benoît Canet" <benoit.canet@irqsave.net>
To: Fam Zheng <famz@redhat.com>
Cc: "Benoît Canet" <benoit.canet@irqsave.net>,
	kwolf@redhat.com, jcody@redhat.com, qemu-devel@nongnu.org,
	armbru@redhat.com, stefanha@redhat.com
Subject: Re: [Qemu-devel] [RFC V3 6/7] block: Create authorizations mechanism for external snapshots.
Date: Wed, 4 Dec 2013 07:34:10 +0100	[thread overview]
Message-ID: <20131204063409.GE2781@irqsave.net> (raw)
In-Reply-To: <529EC7C3.6040504@redhat.com>

Le Wednesday 04 Dec 2013 à 14:12:19 (+0800), Fam Zheng a écrit :
> On 2013年12月04日 13:20, Benoît Canet wrote:
> >Le Wednesday 04 Dec 2013 à 11:47:22 (+0800), Fam Zheng a écrit :
> >>On 2013年12月03日 21:26, Benoît Canet wrote:
> >>>---
> >>>  block.c                   | 64 +++++++++++++++++++++++++++++++++++++++++------
> >>>  block/blkverify.c         |  2 +-
> >>>  include/block/block.h     | 16 +++++++++---
> >>>  include/block/block_int.h |  9 ++++---
> >>>  4 files changed, 75 insertions(+), 16 deletions(-)
> >>>
> >>>diff --git a/block.c b/block.c
> >>>index 8016ff2..0569cb2 100644
> >>>--- a/block.c
> >>>+++ b/block.c
> >>>@@ -4945,21 +4945,69 @@ int bdrv_amend_options(BlockDriverState *bs, QEMUOptionParameter *options)
> >>>      return bs->drv->bdrv_amend_options(bs, options);
> >>>  }
> >>>
> >>>-ExtSnapshotPerm bdrv_check_ext_snapshot(BlockDriverState *bs)
> >>>+/* will be used to recurse on single child block filter until first format
> >>>+ * (single child block filter will store their child in bs->file)
> >>>+ */
> >>>+ExtSnapshotPerm bdrv_generic_check_ext_snapshot(BlockDriverState *bs,
> >>>+                                                BlockDriverState *candidate)
> >>>  {
> >>>-    if (bs->drv->bdrv_check_ext_snapshot) {
> >>>-        return bs->drv->bdrv_check_ext_snapshot(bs);
> >>>+    if (!bs->drv) {
> >>>+        return EXT_SNAPSHOT_FORBIDDEN;
> >>>      }
> >>>
> >>>-    if (bs->file && bs->file->drv && bs->file->drv->bdrv_check_ext_snapshot) {
> >>>-        return bs->file->drv->bdrv_check_ext_snapshot(bs);
> >>>+    if (!bs->drv->authorizations[BS_CANT_SNAPSHOT]) {
> >>
> >>This double negative feels hard to read for me.
> >>
> >>>+        if (bs == candidate) {
> >>>+             return EXT_SNAPSHOT_ALLOWED;
> >>>+        } else {
> >>>+             return EXT_SNAPSHOT_FORBIDDEN;
> >>>+        }
> >>>      }
> >>>
> >>>-    /* external snapshots are allowed by default */
> >>>-    return EXT_SNAPSHOT_ALLOWED;
> >>>+    if (!bs->drv->authorizations[BS_FILTER_PASS_DOWN]) {
> >>>+        return EXT_SNAPSHOT_FORBIDDEN;
> >>>+    }
> >>>+
> >>>+    if (!bs->file) {
> >>>+        return EXT_SNAPSHOT_FORBIDDEN;
> >>>+    }
> >>>+
> >>>+    return bdrv_recurse_check_ext_snapshot(bs->file, candidate);
> >>>  }
> >>>
> >>>-ExtSnapshotPerm bdrv_check_ext_snapshot_forbidden(BlockDriverState *bs)
> >>>+ExtSnapshotPerm bdrv_recurse_check_ext_snapshot(BlockDriverState *bs,
> >>>+                                                BlockDriverState *candidate)
> >>>  {
> >>>+    if (bs->drv && bs->drv->bdrv_check_ext_snapshot) {
> >>>+        return bs->drv->bdrv_check_ext_snapshot(bs, candidate);
> >>>+    }
> >>
> >>Maybe I'm missing something, but if a driver always returns positive
> >>permit, despite of what candidate is (or even it's relevant to bs),
> >>then doesn't it also affect other devices? because...
> >>
> >>>+
> >>>+    return bdrv_generic_check_ext_snapshot(bs, candidate);
> >>>+}
> >>>+
> >>>+/* This function check if the candidate bs has snapshots authorized by going
> >>>+ * down the forest of bs, skipping filters and stopping on the the first bses
> >>>+ * authorizing snapshots
> >>>+ */
> >>>+ExtSnapshotPerm bdrv_check_ext_snapshot(BlockDriverState *candidate)
> >>>+{
> >>>+    BlockDriverState *bs;
> >>>+
> >>>+    /* walk down the bs forest recursively */
> >>>+    QTAILQ_FOREACH(bs, &bdrv_states, device_list) {
> >>
> >>this iterates through all the known graph trees (device_list),
> >>instead of limiting to only the device that candidate belongs to.
> >
> >The recursion termination success is candidate == bs.
> >This make sure that the scan of the other tree of the forest will not return any
> >spurious success.
> >
>
> But the "candidate == bs" check is in
> bdrv_generic_check_ext_snapshot, which gets short-circuited by
> driver implementation if the driver implements it, in
> bdrv_recurse_check_ext_snapshot.
>
> So if I have an "always yes" drv->bdrv_check_ext_snapshot and it
> happens to be the first one in bdrv_states, I will allow all
> snapshot operations.
>

My bad I forgot to document the drv_>bdrv_check_ext_snapshot.
It meant to be recursive and only for twisted block filter like this one (quorum):

static ExtSnapshotPerm quorum_check_ext_snapshot(BlockDriverState *bs,
                                                 BlockDriverState *candidate)
{
    BDRVQuorumState *s = bs->opaque;
    int i;

    for (i = 0; i < s->total; i++) {
        ExtSnapshotPerm perm = bdrv_recurse_check_ext_snapshot(s->bs[i],
                                                               candidate);
        if (perm == EXT_SNAPSHOT_ALLOWED) {
            return EXT_SNAPSHOT_ALLOWED;
        }
    }

    return EXT_SNAPSHOT_FORBIDDEN;
}

Maybe the callback needs a serious rename.

Best regards

Benoît

> Fam

  reply	other threads:[~2013-12-04  6:34 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-03 13:25 [Qemu-devel] [RFC V3 0/7] Giving names to BlockDriverState graph nodes Benoît Canet
2013-12-03 13:25 ` [Qemu-devel] [RFC V3 1/7] block: Add bs->node_name to hold the name of a bs node of the bs graph Benoît Canet
2013-12-04 23:26   ` Eric Blake
2013-12-03 13:26 ` [Qemu-devel] [RFC V3 2/7] block: Allow the user to define "node-name" option Benoît Canet
2013-12-04 23:33   ` Eric Blake
2013-12-03 13:26 ` [Qemu-devel] [RFC V3 3/7] qapi: Add skeletton of command to query a drive bs graph Benoît Canet
2013-12-04  3:10   ` Fam Zheng
2013-12-04 23:46   ` Eric Blake
2013-12-05 14:24     ` Benoît Canet
2013-12-05 14:38       ` Eric Blake
2013-12-05 14:43         ` Benoît Canet
2013-12-05 14:59           ` Eric Blake
2013-12-05 16:37             ` Benoît Canet
2013-12-03 13:26 ` [Qemu-devel] [RFC V3 4/7] qmp: Allow block_passwd to manipulate bs graph nodes Benoît Canet
2013-12-04 23:56   ` Eric Blake
2013-12-05 14:12     ` Benoît Canet
2013-12-03 13:26 ` [Qemu-devel] [RFC V3 5/7] qmp: Allow block_resize " Benoît Canet
2013-12-05  0:01   ` Eric Blake
2013-12-03 13:26 ` [Qemu-devel] [RFC V3 6/7] block: Create authorizations mechanism for external snapshots Benoît Canet
2013-12-04  3:35   ` Fam Zheng
2013-12-04  5:22     ` Benoît Canet
2013-12-04  3:47   ` Fam Zheng
2013-12-04  5:20     ` Benoît Canet
2013-12-04  6:12       ` Fam Zheng
2013-12-04  6:34         ` Benoît Canet [this message]
2013-12-04  7:03           ` Fam Zheng
2013-12-05 14:52             ` Benoît Canet
2013-12-03 13:26 ` [Qemu-devel] [RFC V3 7/7] qmp: Allow to take external snapshots on bs graphs node Benoît Canet
2013-12-04  3:51   ` Fam Zheng
2013-12-04  5:15     ` Benoît Canet
2013-12-05  0:11   ` Eric Blake
2013-12-05 14:16     ` Benoît Canet

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=20131204063409.GE2781@irqsave.net \
    --to=benoit.canet@irqsave.net \
    --cc=armbru@redhat.com \
    --cc=famz@redhat.com \
    --cc=jcody@redhat.com \
    --cc=kwolf@redhat.com \
    --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).