All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Daniel De Graaf <dgdegra@tycho.nsa.gov>
Cc: "Jun Zhu (Intern)" <Jun.Zhu@citrix.com>,
	xen-devel <xen-devel@lists.xensource.com>
Subject: Re: [PATCH] xenbus: add missing wakeup in concurrent read/write
Date: Wed, 08 Sep 2010 09:34:08 +1000	[thread overview]
Message-ID: <4C86CBF0.3040907@goop.org> (raw)
In-Reply-To: <4C865D5A.5040705@tycho.nsa.gov>

 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

  reply	other threads:[~2010-09-07 23:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-07 15:42 [PATCH] xenbus: add missing wakeup in concurrent read/write Daniel De Graaf
2010-09-07 23:34 ` Jeremy Fitzhardinge [this message]
2010-09-08 10:51   ` Jun Zhu (Intern)

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4C86CBF0.3040907@goop.org \
    --to=jeremy@goop.org \
    --cc=Jun.Zhu@citrix.com \
    --cc=dgdegra@tycho.nsa.gov \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.