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
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
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
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