diff options
| author | John Snow <jsnow@redhat.com> | 2018-10-29 16:23:16 -0400 |
|---|---|---|
| committer | John Snow <jsnow@redhat.com> | 2018-10-29 16:23:16 -0400 |
| commit | 0be37c9e19f541643ef407bdafe0282b667ec23c (patch) | |
| tree | 52d7c4eab4a5508b8b45861214ccc17346b8134d /block | |
| parent | 283d7a04f2addcc51468635300208b60c19a0db3 (diff) | |
block/dirty-bitmaps: allow clear on disabled bitmaps
Similarly to merge, it's OK to allow clear operations on disabled
bitmaps, as this condition only means that they are not recording
new writes. We are free to clear it if the user requests it.
Signed-off-by: John Snow <jsnow@redhat.com>
Reviewed-by: Eric Blake <eblake@redhat.com>
Reviewed-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
Message-id: 20181002230218.13949-4-jsnow@redhat.com
Signed-off-by: John Snow <jsnow@redhat.com>
Diffstat (limited to 'block')
| -rw-r--r-- | block/dirty-bitmap.c | 1 |
1 files changed, 0 insertions, 1 deletions
diff --git a/block/dirty-bitmap.c b/block/dirty-bitmap.c index bfccb0ea15..9b9ebd7142 100644 --- a/block/dirty-bitmap.c +++ b/block/dirty-bitmap.c @@ -625,7 +625,6 @@ void bdrv_reset_dirty_bitmap(BdrvDirtyBitmap *bitmap, void bdrv_clear_dirty_bitmap(BdrvDirtyBitmap *bitmap, HBitmap **out) { - assert(bdrv_dirty_bitmap_enabled(bitmap)); assert(!bdrv_dirty_bitmap_readonly(bitmap)); bdrv_dirty_bitmap_lock(bitmap); if (!out) { |