xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Keir Fraser <keir.fraser@eu.citrix.com>
To: Yu Zhiguo <yuzg@cn.fujitsu.com>,
	"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: why xenstore-* hangs if xenstored is not started
Date: Tue, 22 Jun 2010 08:45:04 +0100	[thread overview]
Message-ID: <C8462890.18288%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <4C206713.6030508@cn.fujitsu.com>

On 22/06/2010 08:32, "Yu Zhiguo" <yuzg@cn.fujitsu.com> wrote:

>  Running xenstore-* when xenstored is not started, it will hang and
> cannot accept any signal, e.g. SIGINT.
>  I seems that the process is blocked at accessing '/proc/xen/xenbus'.
> 
>  # mount -t xenfs xenfs /proc/xen/
>  # xenstore-ls
> 
>  call trace:
>  do_ls() -> xs_directory() -> xs_talkv() -> xs_write_all() -> write()
> 
>  BLOCK is no problem but why process cannot accept signal, Any opinion?

Does the xenstore driver in the dom0 kernel put the process into
uninterruptible sleep? The 2.6.18 kernel simply returns -ENODEV in this case
I think. So perhaps pv_ops has different and inferior behaviour. At least
using interruptible sleep would be preferable.

 -- Keir

>  If start xenstored in other console, xenstore-ls executes and then
> receive the signal, seems the signal is pended...

  parent reply	other threads:[~2010-06-22  7:45 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-22  7:32 why xenstore-* hangs if xenstored is not started Yu Zhiguo
2010-06-22  7:44 ` Vincent Hanquez
2010-06-22  7:58   ` Yu Zhiguo
2010-06-22  8:27     ` Vincent Hanquez
2010-06-22  8:46       ` Yu Zhiguo
2010-06-22  7:45 ` Keir Fraser [this message]
2010-06-22  7:56   ` Vincent Hanquez
2010-06-22  8:06     ` Keir Fraser
2010-06-22  8:26       ` Vincent Hanquez
2010-06-22  8:12   ` Yu Zhiguo

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=C8462890.18288%keir.fraser@eu.citrix.com \
    --to=keir.fraser@eu.citrix.com \
    --cc=xen-devel@lists.xensource.com \
    --cc=yuzg@cn.fujitsu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).