From: Stefan Hajnoczi <stefanha@gmail.com>
To: Hitoshi Mitake <mitake.hitoshi@lab.ntt.co.jp>
Cc: sheepdog@lists.wpkg.org, qemu-devel@nongnu.org, mitake.hitoshi@gmail.com
Subject: Re: [Qemu-devel] [PATCH v3 0/2] bugfixes of sheepdog driver for a case of live snapshot
Date: Fri, 6 Jun 2014 14:54:56 +0200 [thread overview]
Message-ID: <20140606125456.GA14322@stefanha-thinkpad> (raw)
In-Reply-To: <1402029312-23953-1-git-send-email-mitake.hitoshi@lab.ntt.co.jp>
On Fri, Jun 06, 2014 at 01:35:10PM +0900, Hitoshi Mitake wrote:
> Current sheepdog driver has two problems in a mechanism of inode
> object reloading for live snapshot. It causes inconsistent state of
> snapshot volumes. A new GC algorithm implemented in sheepdog exposes
> the problems. This patchset contains bugfixes for them.
>
> v3:
> - update commit log
>
> v2:
> - corrrect wrong spelling in the commit log of 2nd patch
>
> Hitoshi Mitake (2):
> sheepdog: fix vdi object update after live snapshot
> sheepdog: reload only header in a case of live snapshot
>
> block/sheepdog.c | 49 +++++++++++++++++++++++++++++--------------------
> 1 files changed, 29 insertions(+), 20 deletions(-)
>
>
Thanks, applied to my block tree:
https://github.com/stefanha/qemu/commits/block
Stefan
prev parent reply other threads:[~2014-06-06 12:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-06 4:35 [Qemu-devel] [PATCH v3 0/2] bugfixes of sheepdog driver for a case of live snapshot Hitoshi Mitake
2014-06-06 4:35 ` [Qemu-devel] [PATCH v3 1/2] sheepdog: fix vdi object update after " Hitoshi Mitake
2014-06-06 4:35 ` [Qemu-devel] [PATCH v3 2/2] sheepdog: reload only header in a case of " Hitoshi Mitake
2014-06-06 6:06 ` [Qemu-devel] [sheepdog] [PATCH v3 0/2] bugfixes of sheepdog driver for " Liu Yuan
2014-06-06 12:54 ` Stefan Hajnoczi [this message]
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=20140606125456.GA14322@stefanha-thinkpad \
--to=stefanha@gmail.com \
--cc=mitake.hitoshi@gmail.com \
--cc=mitake.hitoshi@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).