From: Baoquan He <bhe@redhat.com>
To: Thomas Garnier <thgarnie@google.com>
Cc: Dan Williams <dan.j.williams@intel.com>,
Jeff Moyer <jmoyer@redhat.com>, Ingo Molnar <mingo@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
"linux-nvdimm@lists.01.org" <linux-nvdimm@ml01.01.org>
Subject: Re: KASLR causes intermittent boot failures on some systems
Date: Tue, 25 Apr 2017 09:18:25 +0800 [thread overview]
Message-ID: <20170425011825.GA4622@x1> (raw)
In-Reply-To: <CAJcbSZEWB27HHtP6zVQA+qJJ7uvWqZz+Y-kYFE0aTM2-jj72iQ@mail.gmail.com>
On 04/24/17 at 05:41pm, Thomas Garnier wrote:
> On Mon, Apr 24, 2017 at 4:07 PM, Baoquan He <bhe@redhat.com> wrote:
> > Yeah, according to my debugging tracking, it goes as Dan said. And the
> > is_ram is REGION_DISJOINT. And till arch_add_memory, the parameters
> > passed to arch_add_memory are "arch_add_memory, align_start:0x10000000000, align_size:0x3000000000",
> > seems it's going well.
>
> Hum ok, I hope it was another path given it seems the page table is
> correctly setup on this one.
>
> Maybe looking at the PTEs with and without crash might help? (setting
> this if statement to 1:
> http://lxr.free-electrons.com/source/arch/x86/mm/init_64.c#L360)
The page_size_mask is PG_LEVEL_1G, it should only enter into
phys_pud_init and return.
next prev parent reply other threads:[~2017-04-25 1:18 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-07 14:41 KASLR causes intermittent boot failures on some systems Jeff Moyer
2017-04-07 14:49 ` Thomas Garnier
2017-04-07 14:51 ` Jeff Moyer
2017-04-07 21:25 ` Kees Cook
2017-04-10 15:49 ` Jeff Moyer
2017-04-10 18:13 ` Kees Cook
2017-04-10 18:22 ` Jeff Moyer
2017-04-10 19:03 ` Kees Cook
2017-04-10 19:18 ` Jeff Moyer
2017-04-08 2:51 ` Baoquan He
2017-04-08 4:08 ` Baoquan He
2017-04-08 7:02 ` Dan Williams
2017-04-08 7:52 ` Baoquan He
2017-04-10 15:57 ` Jeff Moyer
2017-04-12 8:24 ` Dave Young
2017-04-12 8:27 ` Dave Young
2017-04-12 8:40 ` Dave Young
2017-04-12 12:52 ` Jeff Moyer
2017-04-19 13:36 ` Baoquan He
2017-04-19 14:27 ` Thomas Garnier
2017-04-19 14:34 ` Dan Williams
2017-04-19 14:56 ` Baoquan He
2017-04-19 14:56 ` Thomas Garnier
2017-04-19 14:55 ` Baoquan He
2017-04-20 13:26 ` Baoquan He
2017-04-24 20:37 ` Thomas Garnier
2017-04-24 20:52 ` Dan Williams
2017-04-24 23:07 ` Baoquan He
2017-04-24 23:18 ` Dan Williams
2017-04-24 23:56 ` Baoquan He
2017-04-25 0:41 ` Thomas Garnier
2017-04-25 1:18 ` Baoquan He [this message]
2017-05-01 11:32 ` Baoquan He
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=20170425011825.GA4622@x1 \
--to=bhe@redhat.com \
--cc=dan.j.williams@intel.com \
--cc=jmoyer@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvdimm@ml01.01.org \
--cc=mingo@kernel.org \
--cc=thgarnie@google.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).