All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Vrabel <david.vrabel@citrix.com>
To: "Vitaly Chernooky" <vitalii.chernookyi@globallogic.com>,
	"Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>
Cc: Boris Ostrovsky <boris.ostrovsky@oracle.com>,
	Embedded-pv-devel@lists.xenproject.org,
	Iurii Konovalenko <iurii.konovalenko@globallogic.com>,
	Ian Campbell <ian.campbell@citrix.com>,
	xen-devel <xen-devel@lists.xen.org>
Subject: Re: Deadlock in /proc/xen/xenbus watch+read on 3.17+ (maybe earlier)
Date: Fri, 20 Mar 2015 10:46:54 +0000	[thread overview]
Message-ID: <550BFA9E.8010102@citrix.com> (raw)
In-Reply-To: <CANZZXhCWhhxgHqonONagnOb0LfoMX2kQx7HPSyZ=sBE-83S6sw@mail.gmail.com>

On 20/03/15 10:38, Vitaly Chernooky wrote:
> So I have finished my investigation and suggest to discuss the simple
> attaches patch.

Looks ok to me.  But this needs to go via the filesystem maintainers,
Cc'ing Linus on it.  You should explain the deadlock in more detail in
the commit message and mention that it fixes a regression and which
commit introduced the regression.

Another solution would be to replace the file with a symlink to
/dev/xen/xenbus.

David

  reply	other threads:[~2015-03-20 10:46 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 [this message]
2015-03-20 11:39                 ` Vitaly Chernooky
2015-03-20 10:41             ` Marek Marczykowski-Górecki
2015-03-19 11:10 ` David Vrabel

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=550BFA9E.8010102@citrix.com \
    --to=david.vrabel@citrix.com \
    --cc=Embedded-pv-devel@lists.xenproject.org \
    --cc=boris.ostrovsky@oracle.com \
    --cc=ian.campbell@citrix.com \
    --cc=iurii.konovalenko@globallogic.com \
    --cc=marmarek@invisiblethingslab.com \
    --cc=vitalii.chernookyi@globallogic.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.