[PULL,06/18] block: Assert that bdrv_release_dirty_bitmap succeeded
diff mbox

Message ID 1473871262-409-7-git-send-email-mreitz@redhat.com
State New
Headers show

Commit Message

Max Reitz Sept. 14, 2016, 4:40 p.m. UTC
From: Fam Zheng <famz@redhat.com>

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>
Reviewed-by: Max Reitz <mreitz@redhat.com>
Signed-off-by: John Snow <jsnow@redhat.com>
Message-id: 1470096763-14033-7-git-send-email-jsnow@redhat.com
Signed-off-by: Max Reitz <mreitz@redhat.com>
 block/dirty-bitmap.c | 3 +++
 1 file changed, 3 insertions(+)

diff mbox

diff --git a/block/dirty-bitmap.c b/block/dirty-bitmap.c
index 860acc9..31d5296 100644
--- a/block/dirty-bitmap.c
+++ b/block/dirty-bitmap.c
@@ -305,6 +305,9 @@  static void bdrv_do_release_matching_dirty_bitmap(BlockDriverState *bs,
+    if (bitmap) {
+        abort();
+    }
 void bdrv_release_dirty_bitmap(BlockDriverState *bs, BdrvDirtyBitmap *bitmap)