Commit 986c28d6 authored by Andrea Arcangeli's avatar Andrea Arcangeli Committed by Christoph Hellwig

fix qemu_aio_flush

qemu_aio_wait by invoking the bh or one of the aio completion
callbacks, could end up submitting new pending aio, breaking the
invariant that qemu_aio_flush returns only when no pending aio is
outstanding (possibly a problem for migration as such).
Signed-off-by: default avatarAndrea Arcangeli <>
Signed-off-by: default avatarChristoph Hellwig <>
Acked-by: default avatarKevin Wolf <>
parent e19252d3
......@@ -103,11 +103,15 @@ void qemu_aio_flush(void)
do {
ret = 0;
* If there are pending emulated aio start them now so flush
* will be able to return 1.
LIST_FOREACH(node, &aio_handlers, node) {
ret |= node->io_flush(node->opaque);
} while (ret > 0);
......@@ -24,9 +24,10 @@ typedef int (AioFlushHandler)(void *opaque);
* outstanding AIO operations have been completed or cancelled. */
void qemu_aio_flush(void);
/* Wait for a single AIO completion to occur. This function will until a
* single AIO opeartion has completed. It is intended to be used as a looping
* primative when simulating synchronous IO based on asynchronous IO. */
/* Wait for a single AIO completion to occur. This function will wait
* until a single AIO event has completed and it will ensure something
* has moved before returning. This can issue new pending aio as
* result of executing I/O completion or bh callbacks. */
void qemu_aio_wait(void);
/* Register a file descriptor and associated callbacks. Behaves very similarly
Markdown is supported
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment