From mboxrd@z Thu Jan  1 00:00:00 1970
From: Jeremy Fitzhardinge <jeremy@goop.org>
Subject: Re: [PATCH] xenbus: add missing wakeup in concurrent
	read/write
Date: Wed, 08 Sep 2010 09:34:08 +1000
Message-ID: <4C86CBF0.3040907@goop.org>
References: <4C865D5A.5040705@tycho.nsa.gov>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <4C865D5A.5040705@tycho.nsa.gov>
List-Unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: Daniel De Graaf <dgdegra@tycho.nsa.gov>
Cc: "Jun Zhu (Intern)" <Jun.Zhu@citrix.com>, xen-devel <xen-devel@lists.xensource.com>
List-Id: xen-devel@lists.xenproject.org

 On 09/08/2010 01:42 AM, Daniel De Graaf wrote:
> If an application has a dedicated read thread watching xenbus and
> another thread writes an XS_WATCH message that generates a synthetic
> "OK" reply, this reply will be enqueued in the buffer without waking up
> the reader. This can cause a deadlock in the application if it then
> waits for the read thread to receive the queued message.
>
> Signed-off-by: Daniel De Graaf <dgdegra@tycho.nsa.gov>

Thanks.  Jun Zhu, does this fix the problem you were reporting?

    J