[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5179A7CE.2050605@zytor.com>
Date: Thu, 25 Apr 2013 15:01:50 -0700
From: "H. Peter Anvin" <hpa@...or.com>
To: Kees Cook <keescook@...omium.org>
CC: linux-kernel@...r.kernel.org, kernel-hardening@...ts.openwall.com,
Thomas Gleixner <tglx@...utronix.de>, Ingo Molnar <mingo@...hat.com>,
x86@...nel.org, Jarkko Sakkinen <jarkko.sakkinen@...el.com>,
Matthew Garrett <mjg@...hat.com>,
Matt Fleming <matt.fleming@...el.com>,
Eric Northup <digitaleric@...gle.com>,
Dan Rosenberg <drosenberg@...curity.com>,
Julien Tinnes <jln@...gle.com>, Will Drewry <wad@...omium.org>
Subject: Re: [PATCH v3 0/6] kernel ASLR
On 04/25/2013 02:54 PM, Kees Cook wrote:
> This continues to build on the tip/kaslr patches for KASLR. This series
> converts the logic to C, and moves both relocation and address selection
> into the decompress_kernel path. Several areas were refactored to allow
> for some code reuse (e.g. CPU flags, kernel command line).
>
> This does not yet attempt to rework the page tables to handle an arbitrary
> physical memory location on x86_64. I would love some suggestions on
> how to do this. :)
>
We *should* already support arbitrary physical memory locations at least
in the kernel proper (the decompressor might need some work.)
We may want to do in the decompressor what we already do in the kernel,
and set up a #PF handler which creates page tables on demand. That way
you can simply treat the entire memory space as a single linear space.
-hpa
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
