qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@redhat.com>
To: Fam Zheng <famz@redhat.com>
Cc: kwolf@redhat.com, jcody@redhat.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2 3/7] block: implement reference count for BlockDriverState
Date: Tue, 30 Jul 2013 16:58:48 +0200	[thread overview]
Message-ID: <20130730145848.GE9018@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <1375170777-31457-4-git-send-email-famz@redhat.com>

On Tue, Jul 30, 2013 at 03:52:53PM +0800, Fam Zheng wrote:
> @@ -1518,6 +1519,9 @@ static void bdrv_move_feature_fields(BlockDriverState *bs_dest,
>      /* dirty bitmap */
>      bs_dest->dirty_bitmap       = bs_src->dirty_bitmap;
>  
> +    /* reference count */
> +    bs_dest->refcnt             = bs_src->refcnt;
> +
>      /* job */
>      bs_dest->in_use             = bs_src->in_use;
>      bs_dest->job                = bs_src->job;

Not sure this is correct, but then bdrv_swap() is hard to reason
about... :)

Imagine an emulated storage controller holds a reference to the
BlockDriverState.  When we create an external snapshot we'll
bdrv_swap(old_top, new_top).

We must not move new_top's refcount into old_top since the old_top
object is still being referenced by the emulated storage controller.
When the emulated storage controller does bdrv_unref() we'll hit the
recount < 0 assertion and be accessing freed memory.

> @@ -4392,6 +4396,24 @@ int64_t bdrv_get_dirty_count(BlockDriverState *bs)
>      }
>  }
>  
> +/* Get a reference to bs */
> +void bdrv_ref(BlockDriverState *bs)
> +{
> +    bs->refcnt++;
> +}
> +
> +/* Release a previously grabbed reference to bs.
> + * If after releasing, reference count is zero, the BlockDriverState is
> + * deleted. */
> +void bdrv_unref(BlockDriverState *bs)
> +{
> +    assert(bs->refcnt > 0);
> +    if (--bs->refcnt == 0) {
> +        bdrv_close(bs);
> +        bdrv_delete(bs);

bdrv_delete() already calls bdrv_close() internally, no need to call
bdrv_close() here.

  parent reply	other threads:[~2013-07-30 14:59 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-30  7:52 [Qemu-devel] [PATCH v2 0/7] Implement reference count for BlockDriverState Fam Zheng
2013-07-30  7:52 ` [Qemu-devel] [PATCH v2 1/7] vvfat: use bdrv_new() to allocate BlockDriverState Fam Zheng
2013-07-30  7:52 ` [Qemu-devel] [PATCH v2 2/7] iscsi: use bdrv_new() instead of stack structure Fam Zheng
2013-07-30  7:52 ` [Qemu-devel] [PATCH v2 3/7] block: implement reference count for BlockDriverState Fam Zheng
2013-07-30 12:16   ` Andreas Färber
2013-07-30 14:50     ` Stefan Hajnoczi
2013-07-30 14:51   ` Jeff Cody
2013-07-30 14:58   ` Stefan Hajnoczi [this message]
2013-07-31  9:51     ` Fam Zheng
2013-08-01  9:30       ` Stefan Hajnoczi
2013-07-30  7:52 ` [Qemu-devel] [PATCH v2 4/7] block: make bdrv_delete() static Fam Zheng
2013-07-30  7:52 ` [Qemu-devel] [PATCH v2 5/7] migration: omit drive ref as we have bdrv_ref now Fam Zheng
2013-07-30  7:52 ` [Qemu-devel] [PATCH v2 6/7] xen_disk: simplify blk_disconnect with refcnt Fam Zheng
2013-07-30  7:52 ` [Qemu-devel] [PATCH v2 7/7] nbd: use BlockDriverState refcnt 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=20130730145848.GE9018@stefanha-thinkpad.redhat.com \
    --to=stefanha@redhat.com \
    --cc=famz@redhat.com \
    --cc=jcody@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=qemu-devel@nongnu.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).