linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Baoquan He <bhe@redhat.com>
To: Jeff Moyer <jmoyer@redhat.com>
Cc: thgarnie@google.com, mingo@kernel.org, dan.j.williams@intel.com,
	linux-kernel@vger.kernel.org, linux-nvdimm@ml01.01.org,
	keescook@chromium.org, dyoung@redhat.com
Subject: Re: KASLR causes intermittent boot failures on some systems
Date: Mon, 1 May 2017 19:32:32 +0800	[thread overview]
Message-ID: <20170501113232.GA24218@x1> (raw)
In-Reply-To: <x49shlk700k.fsf@segfault.boston.devel.redhat.com>

Hi,

The root cause has been found out finally. It's caused by code bug in
sync_global_pgds which is wrong for loop count calculation.

Will post patch.

Thanks
Baoquan

On 04/07/17 at 10:41am, Jeff Moyer wrote:
> Hi,
> 
> commit 021182e52fe01 ("x86/mm: Enable KASLR for physical mapping memory
> regions") causes some of my systems with persistent memory (whether real
> or emulated) to fail to boot with a couple of different crash
> signatures.  The first signature is a NMI watchdog lockup of all but 1
> cpu, which causes much difficulty in extracting useful information from
> the console.  The second variant is an invalid paging request, listed
> below.
> 
> On some systems, I haven't hit this problem at all.  Other systems
> experience a failed boot maybe 20-30% of the time.  To reproduce it,
> configure some emulated pmem on your system.  You can find directions
> for that here: https://nvdimm.wiki.kernel.org/
> 
> Install ndctl (https://github.com/pmem/ndctl).
> Configure the namespace:
> # ndctl create-namespace -f -e namespace0.0 -m memory
> 
> Then just reboot several times (5 should be enough), and hopefully
> you'll hit the issue.
> 
> I've attached both my .config and the dmesg output from a successful
> boot at the end of this mail.
> 

      parent reply	other threads:[~2017-05-01 11:33 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
2017-05-01 11:32 ` Baoquan He [this message]

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=20170501113232.GA24218@x1 \
    --to=bhe@redhat.com \
    --cc=dan.j.williams@intel.com \
    --cc=dyoung@redhat.com \
    --cc=jmoyer@redhat.com \
    --cc=keescook@chromium.org \
    --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).