[libvirt] [PATCH] virLXCMonitorClose: Unlock domain while closing monitor

2013-07-24 Thread Michal Privoznik
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 connecting succeeds, virLXCProcessMonitorInitNotify() is called with @mon-client locked. The

Re: [libvirt] [PATCH] virLXCMonitorClose: Unlock domain while closing monitor

2013-07-24 Thread Daniel P. Berrange
On Wed, Jul 24, 2013 at 12:15:32PM +0200, 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 connecting succeeds,

Re: [libvirt] [PATCH] virLXCMonitorClose: Unlock domain while closing monitor

2013-07-24 Thread Michal Privoznik
On 24.07.2013 12:29, Daniel P. Berrange wrote: On Wed, Jul 24, 2013 at 12:15:32PM +0200, 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

Re: [libvirt] [PATCH] virLXCMonitorClose: Unlock domain while closing monitor

2013-07-24 Thread Daniel P. Berrange
On Wed, Jul 24, 2013 at 01:43:02PM +0200, Michal Privoznik wrote: On 24.07.2013 12:29, Daniel P. Berrange wrote: On Wed, Jul 24, 2013 at 12:15:32PM +0200, Michal Privoznik wrote: There's a race in lxc driver causing a deadlock. If a domain is destroyed immediately after started, the

Re: [libvirt] [PATCH] virLXCMonitorClose: Unlock domain while closing monitor

2013-07-24 Thread Eric Blake
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,