From: John Snow <jsnow@redhat.com>
To: Fam Zheng <famz@redhat.com>, qemu-devel@nongnu.org
Cc: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>,
qemu-block@nongnu.org
Subject: Re: [Qemu-devel] [Qemu-block] [PATCH v3 11/15] block: Assert that bdrv_release_dirty_bitmap succeeded
Date: Mon, 29 Feb 2016 18:05:38 -0500 [thread overview]
Message-ID: <56D4CEC2.3020401@redhat.com> (raw)
In-Reply-To: <1456564857-29160-12-git-send-email-famz@redhat.com>
On 02/27/2016 04:20 AM, Fam Zheng wrote:
> We use a loop over bs->dirty_bitmaps to make sure the caller is
> only releasing a bitmap owned by bs. Let's also assert that in this case
> the caller is releasing a bitmap that does exist.
>
> Signed-off-by: Fam Zheng <famz@redhat.com>
> ---
> block/dirty-bitmap.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/block/dirty-bitmap.c b/block/dirty-bitmap.c
> index a0c5acb..27d33e7 100644
> --- a/block/dirty-bitmap.c
> +++ b/block/dirty-bitmap.c
> @@ -304,6 +304,9 @@ static void bdrv_do_release_matching_dirty_bitmap(BlockDriverState *bs,
> }
> }
> }
> + if (bitmap) {
> + abort();
> + }
> }
>
> void bdrv_release_dirty_bitmap(BlockDriverState *bs, BdrvDirtyBitmap *bitmap)
>
Bad context, but I assume what happens is if we have a bitmap, we have
an early return above, so this should be unreachable.
Reviewed-by: John Snow <jsnow@redhat.com>
next prev parent reply other threads:[~2016-02-29 23:05 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-27 9:20 [Qemu-devel] [PATCH v3 00/15] Dirty bitmap changes for migration/persistence work Fam Zheng
2016-02-27 9:20 ` [Qemu-devel] [PATCH v3 01/15] backup: Use Bitmap to replace "s->bitmap" Fam Zheng
2016-02-27 9:20 ` [Qemu-devel] [PATCH v3 02/15] block: Include hbitmap.h in block.h Fam Zheng
2016-02-27 9:20 ` [Qemu-devel] [PATCH v3 03/15] typedefs: Add BdrvDirtyBitmap Fam Zheng
2016-02-27 9:20 ` [Qemu-devel] [PATCH v3 04/15] block: Move block dirty bitmap code to separate files Fam Zheng
2016-03-07 18:49 ` [Qemu-devel] [Qemu-block] " Max Reitz
2016-03-08 2:38 ` Fam Zheng
2016-02-27 9:20 ` [Qemu-devel] [PATCH v3 05/15] block: Remove unused typedef of BlockDriverDirtyHandler Fam Zheng
2016-02-27 9:20 ` [Qemu-devel] [PATCH v3 06/15] block: Hide HBitmap in block dirty bitmap interface Fam Zheng
2016-03-07 19:11 ` [Qemu-devel] [Qemu-block] " Max Reitz
2016-03-08 2:14 ` Fam Zheng
2016-02-27 9:20 ` [Qemu-devel] [PATCH v3 07/15] HBitmap: Introduce "meta" bitmap to track bit changes Fam Zheng
2016-02-27 9:20 ` [Qemu-devel] [PATCH v3 08/15] tests: Add test code for meta bitmap Fam Zheng
2016-02-29 22:49 ` [Qemu-devel] [Qemu-block] " John Snow
2016-02-27 9:20 ` [Qemu-devel] [PATCH v3 09/15] block: Support meta dirty bitmap Fam Zheng
2016-02-29 23:00 ` [Qemu-devel] [Qemu-block] " John Snow
2016-03-08 2:31 ` Fam Zheng
2016-02-27 9:20 ` [Qemu-devel] [PATCH v3 10/15] block: Add two dirty bitmap getters Fam Zheng
2016-02-27 9:20 ` [Qemu-devel] [PATCH v3 11/15] block: Assert that bdrv_release_dirty_bitmap succeeded Fam Zheng
2016-02-29 23:05 ` John Snow [this message]
2016-02-27 9:20 ` [Qemu-devel] [PATCH v3 12/15] hbitmap: serialization Fam Zheng
2016-02-27 9:20 ` [Qemu-devel] [PATCH v3 13/15] block: BdrvDirtyBitmap serialization interface Fam Zheng
2016-02-27 9:20 ` [Qemu-devel] [PATCH v3 14/15] tests: Add test code for hbitmap serialization Fam Zheng
2016-02-27 9:20 ` [Qemu-devel] [PATCH v3 15/15] block: More operations for meta dirty bitmap 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=56D4CEC2.3020401@redhat.com \
--to=jsnow@redhat.com \
--cc=famz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=vsementsov@virtuozzo.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).