Vladimir Sementsov-Ogievskiy d2c3080e41 block/qcow2: proper locking on bitmap add/remove paths
qmp_block_dirty_bitmap_add and do_block_dirty_bitmap_remove do acquire
aio context since 0a6c86d024c52b. But this is not enough: we also must
lock qcow2 mutex when access in-image metadata. Especially it concerns
freeing qcow2 clusters.

To achieve this, move qcow2_can_store_new_dirty_bitmap and
qcow2_remove_persistent_dirty_bitmap to coroutine context.

Since we work in coroutines in correct aio context, we don't need
context acquiring in blockdev.c anymore, drop it.

Signed-off-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
Reviewed-by: John Snow <jsnow@redhat.com>
Message-id: 20190920082543.23444-4-vsementsov@virtuozzo.com
Signed-off-by: John Snow <jsnow@redhat.com>
2019-10-17 17:02:32 -04:00
..
2019-10-10 10:56:17 +02:00
2019-09-16 14:48:30 +02:00
2019-09-16 14:48:30 +02:00
2019-09-10 08:58:43 +02:00
2019-08-19 17:13:26 +02:00
2019-09-16 14:48:30 +02:00
2019-09-10 08:58:43 +02:00
2019-10-10 10:56:18 +02:00
2018-02-09 05:05:11 +01:00
2019-05-28 20:30:55 +02:00
2019-09-10 08:58:43 +02:00
2019-09-03 14:55:35 +02:00
2019-09-16 14:48:30 +02:00