On 13.09.18 14:52, Kevin Wolf wrote: > bdrv_do_drained_begin/end() assume that they are called with the > AioContext lock of bs held. If we call drain functions from a coroutine > with the AioContext lock held, we yield and schedule a BH to move out of > coroutine context. This means that the lock for the home context of the > coroutine is released and must be re-acquired in the bottom half. > > Signed-off-by: Kevin Wolf <kw...@redhat.com> > --- > include/qemu/coroutine.h | 5 +++++ > block/io.c | 15 +++++++++++++++ > util/qemu-coroutine.c | 5 +++++ > 3 files changed, 25 insertions(+)
I suppose the coroutine lock you mean is the one aio_co_enter() takes? If so: Reviewed-by: Max Reitz <mre...@redhat.com> (Sorry, I still really don't have much understanding of how coroutines, bottom halves, and all nice things like them work.)
signature.asc
Description: OpenPGP digital signature
