From: Kevin Wolf <kwolf@redhat.com>
To: MORITA Kazutaka <morita.kazutaka@lab.ntt.co.jp>
Cc: aliguori@us.ibm.com, sheepdog@lists.wpkg.org,
kvm@vger.kernel.org, qemu-devel@nongnu.org,
fujita.tomonori@lab.ntt.co.jp, avi@redhat.com, hch@lst.de
Subject: [Qemu-devel] Re: [RFC PATCH v2 2/3] block: call the snapshot handlers of the protocol drivers
Date: Fri, 14 May 2010 14:55:03 +0200 [thread overview]
Message-ID: <4BED4827.5010709@redhat.com> (raw)
In-Reply-To: <1273830676-2349-3-git-send-email-morita.kazutaka@lab.ntt.co.jp>
Am 14.05.2010 11:51, schrieb MORITA Kazutaka:
> When snapshot handlers of the format driver is not defined, it is
> better to call the ones of the protocol driver.
>
> This enables us to implement snapshot support in the protocol driver.
>
> Signed-off-by: MORITA Kazutaka <morita.kazutaka@lab.ntt.co.jp>
> int bdrv_snapshot_goto(BlockDriverState *bs,
> @@ -1737,9 +1743,11 @@ int bdrv_snapshot_goto(BlockDriverState *bs,
> BlockDriver *drv = bs->drv;
> if (!drv)
> return -ENOMEDIUM;
> - if (!drv->bdrv_snapshot_goto)
> - return -ENOTSUP;
> - return drv->bdrv_snapshot_goto(bs, snapshot_id);
> + if (drv->bdrv_snapshot_goto)
> + return drv->bdrv_snapshot_goto(bs, snapshot_id);
> + if (bs->file)
> + return bdrv_snapshot_goto(bs->file, snapshot_id);
> + return -ENOTSUP;
> }
During lunch one more thing came to my mind...
For bdrv_snapshot_goto it's probably not that easy for formats other
than raw. Usually the drivers keep some state in memory, and with this
code they won't re-read it after the snapshot has been loaded - which
will lead to an inconsistent state very easily.
I think the right thing to do here is:
1. Call drv->bdrv_close() so that the format driver cleans up, but the
underlying protocol stays open
2. Load the snapshot on the protocol level
3. Call drv->bdrv_open() to load the new state
The other functions in this patch should be okay without re-opening
because they don't change the current state.
Kevin
next prev parent reply other threads:[~2010-05-14 12:56 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-12 10:46 [Qemu-devel] [RFC PATCH 0/2] Sheepdog: distributed storage system for QEMU MORITA Kazutaka
2010-05-12 10:46 ` [Qemu-devel] [RFC PATCH 1/2] close all the block drivers before the qemu process exits MORITA Kazutaka
2010-05-12 14:01 ` Christoph Hellwig
2010-05-12 19:50 ` MORITA Kazutaka
2010-05-12 14:28 ` [Qemu-devel] " Avi Kivity
2010-05-12 20:16 ` MORITA Kazutaka
2010-05-13 2:34 ` MORITA Kazutaka
2010-05-12 10:46 ` [Qemu-devel] [RFC PATCH 2/2] block: add sheepdog driver for distributed storage support MORITA Kazutaka
2010-05-12 11:38 ` [Qemu-devel] [RFC PATCH 0/2] Sheepdog: distributed storage system for QEMU Kevin Wolf
2010-05-12 19:46 ` MORITA Kazutaka
2010-05-13 14:03 ` MORITA Kazutaka
2010-05-14 8:32 ` Kevin Wolf
2010-05-14 9:54 ` MORITA Kazutaka
2010-05-14 10:05 ` Kevin Wolf
2010-05-14 9:51 ` [Qemu-devel] [RFC PATCH v2 0/3] " MORITA Kazutaka
2010-05-17 10:19 ` [Qemu-devel] [RFC PATCH v3 " MORITA Kazutaka
2010-05-17 10:19 ` [Qemu-devel] [RFC PATCH v3 1/3] close all the block drivers before the qemu process exits MORITA Kazutaka
2010-05-17 10:19 ` [Qemu-devel] [RFC PATCH v3 2/3] block: call the snapshot handlers of the protocol drivers MORITA Kazutaka
2010-05-17 11:08 ` Kevin Wolf
2010-05-17 12:19 ` [Qemu-devel] " MORITA Kazutaka
2010-05-17 12:20 ` Kevin Wolf
2010-05-17 13:03 ` MORITA Kazutaka
2010-05-17 10:19 ` [Qemu-devel] [RFC PATCH v3 3/3] block: add sheepdog driver for distributed storage support MORITA Kazutaka
2010-05-14 9:51 ` [Qemu-devel] [RFC PATCH v2 1/3] close all the block drivers before the qemu process exits MORITA Kazutaka
2010-05-14 9:51 ` [Qemu-devel] [RFC PATCH v2 2/3] block: call the snapshot handlers of the protocol drivers MORITA Kazutaka
2010-05-14 12:55 ` Kevin Wolf [this message]
2010-05-14 9:51 ` [Qemu-devel] [RFC PATCH v2 3/3] block: add sheepdog driver for distributed storage support MORITA Kazutaka
2010-05-14 11:08 ` [Qemu-devel] " Kevin Wolf
2010-05-17 10:34 ` MORITA Kazutaka
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=4BED4827.5010709@redhat.com \
--to=kwolf@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=avi@redhat.com \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=hch@lst.de \
--cc=kvm@vger.kernel.org \
--cc=morita.kazutaka@lab.ntt.co.jp \
--cc=qemu-devel@nongnu.org \
--cc=sheepdog@lists.wpkg.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).