On 07/24/2013 04:15 AM, Michal Privoznik wrote: > There's a race in lxc driver causing a deadlock. If a domain is > destroyed immediately after started, the deadlock can occur. When domain > is started, the even loop tries to connect to the monitor. If the s/even/event/ > connecting succeeds, virLXCProcessMonitorInitNotify() is called with > @mon->client locked. The first thing that callee does, is > virObjectLock(vm). So the order of locking is: 1) @mon->client, 2) @vm. > -- Eric Blake eblake redhat com +1-919-301-3266 Libvirt virtualization library http://libvirt.org
Attachment:
signature.asc
Description: OpenPGP digital signature
-- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list