[libvirt] [PATCH 1/2] Remove watches before calling REMOTE_PROC_CLOSE

2010-05-12 Thread jdenemar
From: Jiri Denemark jdene...@redhat.com First calling REMOTE_PROC_CLOSE and then removing watches might lead to a hang as HANGUP event can be triggered before the watches are actually removed but after virConnectPtr is already freed. As a result of that remoteDomainEventFired() would try to lock

Re: [libvirt] [PATCH 1/2] Remove watches before calling REMOTE_PROC_CLOSE

2010-05-12 Thread Daniel Veillard
On Wed, May 12, 2010 at 12:10:18PM +0200, jdene...@redhat.com wrote: From: Jiri Denemark jdene...@redhat.com First calling REMOTE_PROC_CLOSE and then removing watches might lead to a hang as HANGUP event can be triggered before the watches are actually removed but after virConnectPtr is

Re: [libvirt] [PATCH 1/2] Remove watches before calling REMOTE_PROC_CLOSE

2010-05-12 Thread Chris Lalancette
On 05/12/2010 06:10 AM, jdene...@redhat.com wrote: From: Jiri Denemark jdene...@redhat.com First calling REMOTE_PROC_CLOSE and then removing watches might lead to a hang as HANGUP event can be triggered before the watches are actually removed but after virConnectPtr is already freed. As a

Re: [libvirt] [PATCH 1/2] Remove watches before calling REMOTE_PROC_CLOSE

2010-05-12 Thread Daniel P. Berrange
On Wed, May 12, 2010 at 12:10:18PM +0200, jdene...@redhat.com wrote: From: Jiri Denemark jdene...@redhat.com First calling REMOTE_PROC_CLOSE and then removing watches might lead to a hang as HANGUP event can be triggered before the watches are actually removed but after virConnectPtr is