On 15.03.2011 17:55, Peter Lieven wrote:
On 14.03.2011 10:19, Corentin Chary wrote:
On Thu, Mar 10, 2011 at 3:13 PM, Corentin Chary
wrote:
The threaded VNC servers messed up with QEMU fd handlers without
any kind of locking, and that can cause some nasty race conditions.
Using qemu_mutex_loc
On 14.03.2011 10:19, Corentin Chary wrote:
On Thu, Mar 10, 2011 at 3:13 PM, Corentin Chary
wrote:
The threaded VNC servers messed up with QEMU fd handlers without
any kind of locking, and that can cause some nasty race conditions.
Using qemu_mutex_lock_iothread() won't work because vnc_dpy_cp
Am 14.03.2011 um 10:19 schrieb Corentin Chary:
> On Thu, Mar 10, 2011 at 3:13 PM, Corentin Chary
> wrote:
>> The threaded VNC servers messed up with QEMU fd handlers without
>> any kind of locking, and that can cause some nasty race conditions.
>>
>> Using qemu_mutex_lock_iothread() won't work
On Thu, Mar 10, 2011 at 3:13 PM, Corentin Chary
wrote:
> The threaded VNC servers messed up with QEMU fd handlers without
> any kind of locking, and that can cause some nasty race conditions.
>
> Using qemu_mutex_lock_iothread() won't work because vnc_dpy_cpy(),
> which will wait for the current j