From: Major Hayden <major@mhtx.net>
To: Jan Beulich <JBeulich@suse.com>
Cc: xen-devel@lists.xen.org
Subject: Re: Xen BUG at page_alloc.c:1738 (Xen 4.5)
Date: Wed, 20 May 2015 11:52:23 -0500 [thread overview]
Message-ID: <555CBBC7.2070201@mhtx.net> (raw)
In-Reply-To: <555C80EA020000780007C12D@mail.emea.novell.com>
On 05/20/2015 05:41 AM, Jan Beulich wrote:
> Considering that no-one else is seeing this - is this perhaps connected
> to you building Xen with pre-release gcc 5.0.1? This is also because in
> order for the above to indeed occur, mmio_ro_do_page_fault()'s
> put_page() would need to drop the last reference of a page, yet
> page_get_owner_and_reference() doesn't obtain a reference when
> a page is unallocated (and hence unowned), i.e. normally a page
> would have a refcount of at least 2 here. Hence this would be
> possible only due to a race, but the exact same race to be observed
> on different hardware _and_ under an emulator is extremely unlikely.
That could be a possibility. There is one Fedora patch[1] to fix a GCC 5 compile error but that's probably unrelated to the crash.
I'm still hunting around to see what I can figure out.
[1] http://pkgs.fedoraproject.org/cgit/xen.git/tree/?h=f22
--
Major Hayden
next prev parent reply other threads:[~2015-05-20 16:52 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-19 18:06 Xen BUG at page_alloc.c:1738 (Xen 4.5) Major Hayden
2015-05-19 18:16 ` Andrew Cooper
2015-05-20 2:11 ` Major Hayden
2015-05-20 10:41 ` Jan Beulich
2015-05-20 16:52 ` Major Hayden [this message]
2015-05-20 19:51 ` M A Young
-- strict thread matches above, loose matches on Subject: below --
2015-05-29 6:24 Jason Fritcher
2015-05-29 10:09 ` Andrew Cooper
2015-05-29 10:50 ` M A Young
2015-05-29 10:57 ` Andrew Cooper
2015-05-29 11:17 ` M A Young
2015-05-29 18:12 ` Andrew Cooper
2015-05-30 22:07 ` M A Young
2015-05-30 22:43 ` Andrew Cooper
2015-06-01 7:40 ` Jan Beulich
2015-06-01 7:47 ` M A Young
2015-06-06 21:00 ` M A Young
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=555CBBC7.2070201@mhtx.net \
--to=major@mhtx.net \
--cc=JBeulich@suse.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.