From: Stefan Hajnoczi <stefanha@gmail.com>
To: Fam Zheng <famz@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
qemu-devel@nongnu.org, Stefan Hajnoczi <stefanha@redhat.com>,
Benoit Canet <benoit@irqsave.net>
Subject: Re: [Qemu-devel] [PATCH] block: Split BLOCK_OP_TYPE_COMMIT to BLOCK_OP_TYPE_COMMIT_{SOURCE, TARGET}
Date: Wed, 7 Jan 2015 14:13:38 +0000 [thread overview]
Message-ID: <20150107141338.GC22440@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <1410412440-2168-1-git-send-email-famz@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1009 bytes --]
On Thu, Sep 11, 2014 at 01:14:00PM +0800, Fam Zheng wrote:
> Like BLOCK_OP_TYPE_BACKUP_SOURCE and BLOCK_OP_TYPE_BACKUP_TARGET,
> block-commit involves two asymmetric devices.
>
> This change is not user-visible (yet), because commit only works with
> device names.
>
> But once we enable backing reference in blockdev-add, or specifying
> node-name in block-commit command, we don't want the user to start two
> commit jobs on the same backing chain, which will corrupt things because
> of the final bdrv_swap.
>
> Before we have per category blockers, splitting this type is still
> better.
>
> Signed-off-by: Fam Zheng <famz@redhat.com>
> ---
> block.c | 6 +++---
> blockdev.c | 6 +++++-
> include/block/block.h | 3 ++-
> 3 files changed, 10 insertions(+), 5 deletions(-)
Sorry for missing this patch, it was not on my radar since it has no
Reveiwed-by.
Thanks, applied to my block tree:
https://github.com/stefanha/qemu/commits/block
Stefan
[-- Attachment #2: Type: application/pgp-signature, Size: 473 bytes --]
prev parent reply other threads:[~2015-01-07 14:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-11 5:14 [Qemu-devel] [PATCH] block: Split BLOCK_OP_TYPE_COMMIT to BLOCK_OP_TYPE_COMMIT_{SOURCE, TARGET} Fam Zheng
2015-01-07 14:13 ` 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=20150107141338.GC22440@stefanha-thinkpad.redhat.com \
--to=stefanha@gmail.com \
--cc=benoit@irqsave.net \
--cc=famz@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).