qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Fam Zheng <famz@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: kwolf@redhat.com, jcody@redhat.com, hbrock@redhat.com,
	qemu-devel@nongnu.org, rjones@redhat.com, imain@redhat.com,
	stefanha@redhat.com, pbonzini@redhat.com
Subject: Re: [Qemu-devel] [PATCH v19 07/16] block: Add backing_blocker in BlockDriverState
Date: Tue, 20 May 2014 11:39:27 +0800	[thread overview]
Message-ID: <20140520033927.GD7688@T430.nay.redhat.com> (raw)
In-Reply-To: <871tvpa56o.fsf@blackfin.pond.sub.org>

On Mon, 05/19 22:23, Markus Armbruster wrote:
> Eric Blake <eblake@redhat.com> writes:
> 
> > On 05/11/2014 07:35 PM, Fam Zheng wrote:
> >> This makes use of op_blocker and blocks all the operations except for
> >> commit target, on each BlockDriverState->backing_hd.
> >> 
> >> The asserts for op_blocker in bdrv_swap are removed because with this
> >> change, the target of block commit has at least the backing blocker of
> >> its child, so the assertion is not true. Callers should do their check.
> >> 
> >> Signed-off-by: Fam Zheng <famz@redhat.com>
> >> ---
> >>  block.c                   | 24 ++++++++++++++++++++----
> >>  block/mirror.c            |  1 +
> >>  include/block/block_int.h |  3 +++
> >>  3 files changed, 24 insertions(+), 4 deletions(-)
> >> 
> >> diff --git a/block.c b/block.c
> >> index ec26a2b..8155e68 100644
> >> --- a/block.c
> >> +++ b/block.c
> >> @@ -1097,14 +1097,31 @@ fail:
> >>  void bdrv_set_backing_hd(BlockDriverState *bs, BlockDriverState *backing_hd)
> >>  {
> >>  
> >> +    if (bs->backing_hd) {
> >> +        assert(error_is_set(&bs->backing_blocker));
> >
> > error_is_set() is going away.  Please don't use it.
> > https://lists.gnu.org/archive/html/qemu-devel/2014-05/msg03801.html
> >
> > This can just be assert(bs->backing_blocker).
> 
> Yes.  See commit 0fb6395.  Another instance in PATCH 14.

Yes.

> 
> >> +        bdrv_op_unblock_all(bs->backing_hd, bs->backing_blocker);
> >> +    } else if (backing_hd) {
> >> +        error_setg(&bs->backing_blocker,
> >> +                   "device is used as backing hd of '%s'",
> >> +                   bs->device_name);
> >> +    }
> >> +
> >>      bs->backing_hd = backing_hd;
> >>      if (!backing_hd) {
> >> +        if (error_is_set(&bs->backing_blocker)) {
> >> +            error_free(bs->backing_blocker);
> >
> > if (bs->backing_blocker) {
> 
> Actually, unconditional error_free(bs->backing_blocker) is fine.
> 

Thanks, will update.

Fam

  reply	other threads:[~2014-05-20  3:39 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-12  1:35 [Qemu-devel] [PATCH v19 00/16] Drop in_use from BlockDriverState and enable point-in-time snapshot exporting over NBD Fam Zheng
2014-05-12  1:35 ` [Qemu-devel] [PATCH v19 01/16] vmdk: Optimize cluster allocation Fam Zheng
2014-05-14 14:00   ` Fam Zheng
2014-05-12  1:35 ` [Qemu-devel] [PATCH v19 02/16] block: Add BlockOpType enum Fam Zheng
2014-05-19 13:55   ` Markus Armbruster
2014-05-19 15:53   ` Eric Blake
2014-05-19 16:15     ` Markus Armbruster
2014-05-20  3:09       ` Fam Zheng
2014-05-12  1:35 ` [Qemu-devel] [PATCH v19 03/16] block: Introduce op_blockers to BlockDriverState Fam Zheng
2014-05-19 14:10   ` Markus Armbruster
2014-05-19 14:37     ` Kevin Wolf
2014-05-19 15:37       ` Jeff Cody
2014-05-20 11:43         ` Markus Armbruster
2014-05-12  1:35 ` [Qemu-devel] [PATCH v19 04/16] block: Replace in_use with operation blocker Fam Zheng
2014-05-19 14:28   ` Markus Armbruster
2014-05-20  3:26     ` Fam Zheng
2014-05-12  1:35 ` [Qemu-devel] [PATCH v19 05/16] block: Move op_blocker check from block_job_create to its caller Fam Zheng
2014-05-12  1:35 ` [Qemu-devel] [PATCH v19 06/16] block: Add bdrv_set_backing_hd() Fam Zheng
2014-05-12  1:35 ` [Qemu-devel] [PATCH v19 07/16] block: Add backing_blocker in BlockDriverState Fam Zheng
2014-05-19 19:35   ` Eric Blake
2014-05-19 20:23     ` Markus Armbruster
2014-05-20  3:39       ` Fam Zheng [this message]
2014-05-12  1:35 ` [Qemu-devel] [PATCH v19 08/16] block: Parse "backing" option to reference existing BDS Fam Zheng
2014-05-12  1:35 ` [Qemu-devel] [PATCH v19 09/16] block: Support dropping active in bdrv_drop_intermediate Fam Zheng
2014-05-19 19:38   ` Eric Blake
2014-05-20  3:53     ` Fam Zheng
2014-05-12  1:35 ` [Qemu-devel] [PATCH v19 10/16] stream: Use bdrv_drop_intermediate and drop close_unused_images Fam Zheng
2014-05-12  1:35 ` [Qemu-devel] [PATCH v19 11/16] commit: Use bdrv_drop_intermediate Fam Zheng
2014-05-12  1:35 ` [Qemu-devel] [PATCH v19 12/16] qmp: Add command 'blockdev-backup' Fam Zheng
2014-05-12  1:35 ` [Qemu-devel] [PATCH v19 13/16] block: Allow backup on referenced named BlockDriverState Fam Zheng
2014-05-12  1:35 ` [Qemu-devel] [PATCH v19 14/16] block: Add blockdev-backup to transaction Fam Zheng
2014-05-12  1:35 ` [Qemu-devel] [PATCH v19 15/16] qemu-iotests: Test blockdev-backup in 055 Fam Zheng
2014-05-19 19:46   ` Eric Blake
2014-05-20  3:56     ` Fam Zheng
2014-05-12  1:35 ` [Qemu-devel] [PATCH v19 16/16] qemu-iotests: Image fleecing test case 089 Fam Zheng

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=20140520033927.GD7688@T430.nay.redhat.com \
    --to=famz@redhat.com \
    --cc=armbru@redhat.com \
    --cc=hbrock@redhat.com \
    --cc=imain@redhat.com \
    --cc=jcody@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=rjones@redhat.com \
    --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).