block: Fix AioContext switch for drained node

When a drained node changes its AioContext, we need to move its
aio_disable_external() to the new context, too.

Without this fix, drain_end will try to reenable the new context, which
has never been disabled, so an assertion failure is triggered.

Signed-off-by: Kevin Wolf <kwolf@redhat.com>
Reviewed-by: Eric Blake <eblake@redhat.com>
This commit is contained in:
Kevin Wolf 2019-02-08 16:51:17 +01:00
parent 6c75d761d0
commit e64f25f30b

View File

@ -5227,6 +5227,9 @@ void bdrv_detach_aio_context(BlockDriverState *bs)
bdrv_detach_aio_context(child->bs); bdrv_detach_aio_context(child->bs);
} }
if (bs->quiesce_counter) {
aio_enable_external(bs->aio_context);
}
bs->aio_context = NULL; bs->aio_context = NULL;
} }
@ -5240,6 +5243,10 @@ void bdrv_attach_aio_context(BlockDriverState *bs,
return; return;
} }
if (bs->quiesce_counter) {
aio_disable_external(new_context);
}
bs->aio_context = new_context; bs->aio_context = new_context;
QLIST_FOREACH(child, &bs->children, next) { QLIST_FOREACH(child, &bs->children, next) {