All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Vrabel <david.vrabel@citrix.com>
To: "Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>,
	xen-devel <xen-devel@lists.xen.org>
Cc: Boris Ostrovsky <boris.ostrovsky@oracle.com>,
	David Vrabel <david.vrabel@citrix.com>
Subject: Re: Deadlock in /proc/xen/xenbus watch+read on 3.17+ (maybe earlier)
Date: Thu, 19 Mar 2015 11:10:38 +0000	[thread overview]
Message-ID: <550AAEAE.1090609@citrix.com> (raw)
In-Reply-To: <20150319011911.GA29029@mail-itl>

On 19/03/15 01:19, Marek Marczykowski-Górecki wrote:
> Hi,
> 
> I've hit some deadlock in kernel xenstore client exposed via
> /proc/xen/xenbus. Steps to reproduce are simple:
> int main() {
> 	struct xs_handle *xs;
> 	xs = xs_open(0);
> 	xs_watch(xs, "domid", "token");
> 	xs_read(xs, 0, "name", NULL);
> 	return 0;
> }

This test program works for me on 4.0-rc4 in a dom0 and domU.  I also
don't see any xenbus changes in the kernel that could cause a regression
like this.

Perhaps you not running a vanilla kernel?

David

      parent reply	other threads:[~2015-03-19 11:10 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-19  1:19 Deadlock in /proc/xen/xenbus watch+read on 3.17+ (maybe earlier) Marek Marczykowski-Górecki
2015-03-19 10:38 ` Ian Campbell
2015-03-19 12:10   ` Iurii Konovalenko
2015-03-19 12:32     ` [Embedded-pv-devel] " Vitaly Chernooky
2015-03-19 13:00     ` David Vrabel
2015-03-19 13:10       ` Vitaly Chernooky
2015-03-20  4:04         ` Marek Marczykowski-Górecki
2015-03-20  9:58           ` Vitaly Chernooky
2015-03-20 10:08           ` Vitaly Chernooky
2015-03-20 10:38             ` Vitaly Chernooky
2015-03-20 10:46               ` David Vrabel
2015-03-20 11:39                 ` Vitaly Chernooky
2015-03-20 10:41             ` Marek Marczykowski-Górecki
2015-03-19 11:10 ` David Vrabel [this message]

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=550AAEAE.1090609@citrix.com \
    --to=david.vrabel@citrix.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=marmarek@invisiblethingslab.com \
    --cc=xen-devel@lists.xen.org \
    /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.