From: Stefan Bader <stefan.bader@canonical.com>
To: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Cc: Bastian Blank <waldi@debian.org>, Ian Campbell <ijc@hellion.org.uk>
Subject: Re: xen-4.6: xenstored crashes during domain->interface access
Date: Thu, 28 Jan 2016 09:50:37 +0100 [thread overview]
Message-ID: <56A9D65D.2080700@canonical.com> (raw)
In-Reply-To: <56A7513F.9040504@canonical.com>
[-- Attachment #1.1: Type: text/plain, Size: 1636 bytes --]
On 26.01.2016 11:58, Stefan Bader wrote:
> Hi,
>
> while playing around with xen-4.6 I stumbled over an odd problem and am
> wondering whether anybody has seen the same. A method to relatively quickly
> reproduce this for me seems to:
>
> - Start one domU (PV or HVM does not seem to matter)
> - Repeatedly call xenstore-ls a few times
>
> I think I never got beyond 10 repeats when the xenstore-ls call suddenly locks
> up and xenstored crashes with a SIGBUS error. In the majority of cases (I think
> I saw one different), the crash happens while accessing conn->domain->interface
> in tools/xenstore/xenstored_domain.c:domain_can_read().
> Looking at the corefile produced by xenstored I now got at least one case where
> the pointer still matches the previously mapped value. Though I think I had also
> at least one run (with less debugging added) where it seemed to be really wrong.
> There is more info at [1] in case someone is interested.
>
> I need to repeat a few more times to see how consistent the whole thing is. Does
> this happen for anybody else? Any advice what I should look at (in the sense of
> gathering better data)?
Just as an update and confirmation for Ian and Bastian: Debian testing is fine.
I have not dug into the specifics but its not the Xen package side at all.
Something in our 4.3 kernel causes this. Unfortunately without any hint in
dmesg. But since we move to 4.4 soon and I cannot reproduce it with the pending
4.4 build it seems good enough to me.
-Stefan
>
> Thanks,
> Stefan
>
> [1] https://bugs.launchpad.net/ubuntu/+source/xen/+bug/1538049
>
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-01-28 8:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-26 10:58 xen-4.6: xenstored crashes during domain->interface access Stefan Bader
2016-01-28 8:50 ` Stefan Bader [this message]
2016-01-28 9:39 ` Ian Campbell
2016-01-28 10:05 ` Stefan Bader
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=56A9D65D.2080700@canonical.com \
--to=stefan.bader@canonical.com \
--cc=ijc@hellion.org.uk \
--cc=waldi@debian.org \
--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 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).