From mboxrd@z Thu Jan  1 00:00:00 1970
From: Chris Webb <chris@arachsys.com>
Subject: Re: [Qemu-devel] Re: qemu-kvm 0.12.2 VNC segfault
Date: Mon, 22 Feb 2010 19:06:47 +0000
Message-ID: <20100222190646.GE2312@arachsys.com>
References: <20100221172358.GH4894@arachsys.com>
 <4B82462A.7050903@redhat.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org
To: Avi Kivity <avi@redhat.com>
Return-path: <kvm-owner@vger.kernel.org>
Received: from alpha.arachsys.com ([91.203.57.7]:49234 "EHLO
	alpha.arachsys.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1752872Ab0BVTGv (ORCPT <rfc822;kvm@vger.kernel.org>);
	Mon, 22 Feb 2010 14:06:51 -0500
Content-Disposition: inline
In-Reply-To: <4B82462A.7050903@redhat.com>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

Avi Kivity <avi@redhat.com> writes:

> On 02/21/2010 07:23 PM, Chris Webb wrote:
> >Some sort of race where a client disconnects and is removed from the client
> >list while the vnc_refresh() loop is iterating over it, maybe?
> 
> Looks like c727a05459, and high time for 0.12.3.  Anthony?

Ah yes, looks like this was exactly the case that commit was trying to
prevent. Thanks!

Best wishes,

Chris.