Description of problem:
In block/gluster.c, we have
gluster_finish_aiocb
{
if (retval != sizeof(acb)) {
qemu_mutex_lock_iothread(); /* We are in gluster thread context */
...
qemu_mutex_unlock_iothread();
}
}
qemu tools, e.g. qemu-img, might race here because qemu_mutex_{lock,unlock}_iothread are a nop operation and gluster_finish_aiocb is in the gluster thread context.
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
This issue affects upstream and rhel7 qemu as well.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
http://rhn.redhat.com/errata/RHSA-2013-1553.html
Description of problem: In block/gluster.c, we have gluster_finish_aiocb { if (retval != sizeof(acb)) { qemu_mutex_lock_iothread(); /* We are in gluster thread context */ ... qemu_mutex_unlock_iothread(); } } qemu tools, e.g. qemu-img, might race here because qemu_mutex_{lock,unlock}_iothread are a nop operation and gluster_finish_aiocb is in the gluster thread context. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: This issue affects upstream and rhel7 qemu as well.