From: "H. Peter Anvin" <hpa@linux.intel.com>
To: Fengguang Wu <fengguang.wu@intel.com>, Kees Cook <keescook@chromium.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [x86, kaslr] BUG: kernel boot hang
Date: Tue, 14 Jan 2014 08:02:26 -0800 [thread overview]
Message-ID: <52D55F92.8040108@linux.intel.com> (raw)
In-Reply-To: <20140114133125.GB26942@localhost>
On 01/14/2014 05:31 AM, Fengguang Wu wrote:
> Greetings,
>
> I got the below dmesg and the first bad commit is
>
> commit 82fa9637a2ba285bcc7c5050c73010b2c1b3d803
> Author: Kees Cook <keescook@chromium.org>
> AuthorDate: Thu Oct 10 17:18:16 2013 -0700
> Commit: H. Peter Anvin <hpa@linux.intel.com>
> CommitDate: Sun Oct 13 03:12:19 2013 -0700
>
> x86, kaslr: Select random position from e820 maps
>
> Counts available alignment positions across all e820 maps, and chooses
> one randomly for the new kernel base address, making sure not to collide
> with unsafe memory areas.
>
> Signed-off-by: Kees Cook <keescook@chromium.org>
> Link: http://lkml.kernel.org/r/1381450698-28710-5-git-send-email-keescook@chromium.org
> Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
>
> Note that there are many other warning/errors and it's not very
> reproducible, so this report might be wrong.
>
> ===================================================
> PARENT COMMIT NOT CLEAN. LOOK OUT FOR WRONG BISECT!
> ===================================================
>
I wonder if this is in any way related to the fact that the ELF parser
we have in the decompressor is quite frankly complete crap... it assumes
that all sections can only be moved downward.
-hpa
next prev parent reply other threads:[~2014-01-14 16:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-14 13:31 [x86, kaslr] BUG: kernel boot hang Fengguang Wu
2014-01-14 16:02 ` H. Peter Anvin [this message]
2014-01-14 18:32 ` Kees Cook
2014-01-14 19:19 ` H. Peter Anvin
2014-01-14 18:26 ` Kees Cook
2014-01-14 18:47 ` H. Peter Anvin
2014-01-15 12:10 ` Fengguang Wu
2014-01-14 22:33 ` Kees Cook
2014-01-14 23:23 ` H. Peter Anvin
2014-01-14 23:31 ` Kees Cook
2014-01-14 23:45 ` H. Peter Anvin
2014-01-15 12:37 ` Fengguang Wu
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=52D55F92.8040108@linux.intel.com \
--to=hpa@linux.intel.com \
--cc=fengguang.wu@intel.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.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).