qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [PULL 19/43] rcu: init rcu_registry_lock after fork


From: Paolo Bonzini
Subject: Re: [Qemu-devel] [PULL 19/43] rcu: init rcu_registry_lock after fork
Date: Wed, 16 Sep 2015 14:38:10 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0


On 16/09/2015 14:37, Gerd Hoffmann wrote:
> On Mi, 2015-09-09 at 15:49 +0200, Paolo Bonzini wrote:
>> > From: "Emilio G. Cota" <address@hidden>
>> > 
>> > We were unlocking this lock after fork, which is wrong since
>> > only the thread that holds a mutex is allowed to unlock it.
> This breaks libvirt capability probing.  I see qemu running:
> 
> /home/kraxel/projects/qemu/build-default/x86_64-softmmu/qemu-system-x86_64 -S 
> -no-user-config -nodefaults -nographic -M none -qmp 
> unix:/var/lib/libvirt/qemu/capabilities.monitor.sock,server,nowait -pidfile 
> /var/lib/libvirt/qemu/capabilities.pidfile -daemonize
> 
> and libvirt is stuck until I kill qemu.

Yes, Laszlo reported this already.  The patch was included by mistake
and I've already sent a revert.

Paolo



reply via email to

[Prev in Thread] Current Thread [Next in Thread]