From: Kees Cook <keescook@chromium.org>
To: Jason Yan <yanaijie@huawei.com>
Cc: oss@buserror.net, kernel-hardening@lists.openwall.com,
linux-kernel@vger.kernel.org, npiggin@gmail.com,
diana.craciun@nxp.com, paulus@samba.org,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH 0/6] implement KASLR for powerpc/fsl_booke/64
Date: Wed, 20 Nov 2019 10:51:10 -0800 [thread overview]
Message-ID: <201911201050.9182A9DC@keescook> (raw)
In-Reply-To: <20191115093209.26434-1-yanaijie@huawei.com>
On Fri, Nov 15, 2019 at 05:32:03PM +0800, Jason Yan wrote:
> This is a try to implement KASLR for Freescale BookE64 which is based on
> my earlier implementation for Freescale BookE32:
> https://patchwork.ozlabs.org/project/linuxppc-dev/list/?series=131718
Whee! :) I've updated https://github.com/KSPP/linux/issues/3 with a link
to this current series.
--
Kees Cook
prev parent reply other threads:[~2019-11-20 18:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-15 9:32 [PATCH 0/6] implement KASLR for powerpc/fsl_booke/64 Jason Yan
2019-11-15 9:32 ` [PATCH 1/6] powerpc/fsl_booke/kaslr: refactor kaslr_legal_offset() and kaslr_early_init() Jason Yan
2019-11-15 9:32 ` [PATCH 2/6] powerpc/fsl_booke/64: introduce reloc_kernel_entry() helper Jason Yan
2019-11-15 9:32 ` [PATCH 3/6] powerpc/fsl_booke/64: implement KASLR for fsl_booke64 Jason Yan
2019-11-15 9:32 ` [PATCH 4/6] powerpc/fsl_booke/64: do not clear the BSS for the second pass Jason Yan
2019-11-15 9:32 ` [PATCH 5/6] powerpc/fsl_booke/64: clear the original kernel if randomized Jason Yan
2019-11-15 9:32 ` [PATCH 6/6] powerpc/fsl_booke/kaslr: rename kaslr-booke32.rst to kaslr-booke.rst and add 64bit part Jason Yan
2019-11-20 18:51 ` Kees Cook [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=201911201050.9182A9DC@keescook \
--to=keescook@chromium.org \
--cc=diana.craciun@nxp.com \
--cc=kernel-hardening@lists.openwall.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=npiggin@gmail.com \
--cc=oss@buserror.net \
--cc=paulus@samba.org \
--cc=yanaijie@huawei.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).