From: Thomas Gleixner <tglx@linutronix.de>
To: Dave Jiang <dave.jiang@intel.com>
Cc: mingo@redhat.com, hpa@zytor.com, keescook@chromium.org,
bhe@redhat.com, linux-nvdimm@ml01.01.org, x86@kernel.org,
david@fromorbit.com, linux-kernel@vger.kernel.org,
dan.j.williams@intel.com
Subject: Re: [PATCH v7] x86: fix kaslr and memmap collision
Date: Wed, 25 Jan 2017 11:47:47 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.20.1701251147350.3728@nanos> (raw)
In-Reply-To: <148417664156.131935.2248592164852799738.stgit@djiang5-desk3.ch.intel.com>
On Wed, 11 Jan 2017, Dave Jiang wrote:
> CONFIG_RANDOMIZE_BASE relocates the kernel to a random base address.
> However it does not take into account the memmap= parameter passed in from
> the kernel cmdline. This results in the kernel sometimes being put in
> the middle of memmap. Teaching kaslr to not insert the kernel in
> memmap defined regions. We will support up to 4 memmap regions. Any
> additional regions will cause kaslr to disable. The mem_avoid set has
> been augmented to add up to 4 unusable regions of memmaps provided by the
> user to exclude those regions from the set of valid address range to insert
> the uncompressed kernel image. The nn@ss ranges will be skipped by the
> mem_avoid set since it indicates memory useable.
>
> Signed-off-by: Dave Jiang <dave.jiang@intel.com>
> Acked-by: Kees Cook <keescook@chromium.org>
> Acked-by: Baoquan He <bhe@redhat.com>
Reviewed-by: Thomas Gleixner <tglx@linutronix.de>
next prev parent reply other threads:[~2017-01-25 10:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-11 23:20 Dave Jiang
2017-01-25 10:47 ` Thomas Gleixner [this message]
2017-01-25 11:43 ` [tip:x86/boot] x86/boot: Fix KASLR and memmap= collision tip-bot for Dave Jiang
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=alpine.DEB.2.20.1701251147350.3728@nanos \
--to=tglx@linutronix.de \
--cc=bhe@redhat.com \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=david@fromorbit.com \
--cc=hpa@zytor.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvdimm@ml01.01.org \
--cc=mingo@redhat.com \
--cc=x86@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
all inboxes | Powered by JetHome®