From: Matthew Wilcox <willy@infradead.org>
To: Jan Beulich <JBeulich@suse.com>
Cc: Jason Andryuk <jandryuk@gmail.com>,
bugzilla-daemon@bugzilla.kernel.org,
Andrew Cooper <andrew.cooper3@citrix.com>,
linux-mm@kvack.org, akpm@linux-foundation.org,
xen-devel@lists.xen.org,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
labbott@redhat.com, Juergen Gross <jgross@suse.com>
Subject: Re: [Xen-devel] [Bug 198497] handle_mm_fault / xen_pmd_val / radix_tree_lookup_slot Null pointer
Date: Sat, 21 Apr 2018 07:35:08 -0700 [thread overview]
Message-ID: <20180421143508.GB14610@bombadil.infradead.org> (raw)
In-Reply-To: <5ADA0F1502000078001BD1D2@prv1-mh.provo.novell.com>
On Fri, Apr 20, 2018 at 10:02:29AM -0600, Jan Beulich wrote:
> >>>> Skylake 32bit PAE Dom0:
> >>>> Bad swp_entry: 80000000
> >>>> mm/swap_state.c:683: bad pte d3a39f1c(8000000400000000)
> >>>>
> >>>> Ivy Bridge 32bit PAE Dom0:
> >>>> Bad swp_entry: 40000000
> >>>> mm/swap_state.c:683: bad pte d3a05f1c(8000000200000000)
> >>>>
> >>>> Other 32bit DomU:
> >>>> Bad swp_entry: 4000000
> >>>> mm/swap_state.c:683: bad pte e2187f30(8000000200000000)
> >>>>
> >>>> Other 32bit:
> >>>> Bad swp_entry: 2000000
> >>>> mm/swap_state.c:683: bad pte ef3a3f38(8000000100000000)
> As said in my previous reply - both of the bits Andrew has mentioned can
> only ever be set when the present bit is also set (which doesn't appear to
> be the case here). The set bits above are actually in the range of bits
> designated to the address, which Xen wouldn't ever play with.
Is it relevant that all the crashes we've seen are with PAE in the guest?
Is it possible that Xen thinks the guest is not using PAE?
next prev parent reply other threads:[~2018-04-21 14:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-198497-200779@https.bugzilla.kernel.org/>
[not found] ` <bug-198497-200779-43rwxa1kcg@https.bugzilla.kernel.org/>
2018-04-20 13:10 ` [Bug 198497] handle_mm_fault / xen_pmd_val / radix_tree_lookup_slot Null pointer Jason Andryuk
2018-04-20 13:39 ` Matthew Wilcox
2018-04-20 15:20 ` Jason Andryuk
2018-04-20 15:25 ` [Xen-devel] " Andrew Cooper
2018-04-20 15:40 ` Andrew Cooper
2018-04-20 15:42 ` Jan Beulich
2018-04-20 15:52 ` Jason Andryuk
2018-04-20 16:00 ` Andrew Cooper
2018-04-20 16:02 ` Jan Beulich
2018-04-20 19:20 ` Boris Ostrovsky
2018-04-21 6:17 ` Juergen Gross
2018-04-21 14:35 ` Matthew Wilcox [this message]
2018-04-22 5:50 ` Juergen Gross
2018-04-23 8:17 ` Juergen Gross
2018-09-04 12:54 ` Jason Andryuk
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=20180421143508.GB14610@bombadil.infradead.org \
--to=willy@infradead.org \
--cc=JBeulich@suse.com \
--cc=akpm@linux-foundation.org \
--cc=andrew.cooper3@citrix.com \
--cc=boris.ostrovsky@oracle.com \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=jandryuk@gmail.com \
--cc=jgross@suse.com \
--cc=labbott@redhat.com \
--cc=linux-mm@kvack.org \
--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 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).