Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <201907260914.E37F9B041@keescook>
Date: Fri, 26 Jul 2019 09:15:57 -0700
From: Kees Cook <keescook@...omium.org>
To: Jason Yan <yanaijie@...wei.com>
Cc: mpe@...erman.id.au, linuxppc-dev@...ts.ozlabs.org,
	diana.craciun@....com, christophe.leroy@....fr,
	benh@...nel.crashing.org, paulus@...ba.org, npiggin@...il.com,
	kernel-hardening@...ts.openwall.com, linux-kernel@...r.kernel.org,
	wangkefeng.wang@...wei.com, yebin10@...wei.com,
	thunder.leizhen@...wei.com, jingxiangfeng@...wei.com,
	fanchengyang@...wei.com
Subject: Re: [RFC PATCH 00/10] implement KASLR for powerpc/fsl_booke/32

On Fri, Jul 26, 2019 at 03:20:26PM +0800, Jason Yan wrote:
> The boot code only maps one 64M zone at early start. If the kernel crosses
> two 64M zones, we need to map two 64M zones. Keep the kernel in one 64M
> saves a lot of complex codes.

Ah-ha. Gotcha. Thanks for the clarification.

> Yes, if this feature can be accepted, I will start to work with powerpc64
> KASLR and other things like CONFIG_RANDOMIZE_MEMORY.

Awesome. :)

-- 
Kees Cook

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.