From: Daniel Micay <danielmicay@gmail.com>
To: Kees Cook <keescook@chromium.org>, Rik van Riel <riel@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
"kernel-hardening@lists.openwall.com"
<kernel-hardening@lists.openwall.com>,
Ingo Molnar <mingo@kernel.org>, Oleg Nesterov <oleg@redhat.com>,
Larry Woodman <lwoodman@redhat.com>,
mhocko@suse.de, Will Deacon <will.deacon@arm.com>,
"benh@kernel.crashing.org" <benh@kernel.crashing.org>
Subject: Re: [kernel-hardening] [PATCH 0/6] move mmap_area and PIE binaries away from the stack
Date: Sat, 03 Jun 2017 08:14:38 -0400 [thread overview]
Message-ID: <1496492078.21640.1.camel@gmail.com> (raw)
In-Reply-To: <CAGXu5jLfUj9TP6=nVcBy43-Etz6NAeA5kStEpwNRfNNLATEKjQ@mail.gmail.com>
On Fri, 2017-06-02 at 21:37 -0700, Kees Cook wrote:
>
> Patches 3 and 4 need some (minor?) adjustments
It's currently a bug fix. Doing something further would be more than
fixing the bug and should probably be separate.
prev parent reply other threads:[~2017-06-03 12:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-02 15:20 [PATCH 0/6] move mmap_area and PIE binaries away from the stack riel
2017-06-02 15:20 ` [PATCH 1/6] binfmt_elf: document load_bias a little bit riel
2017-06-02 19:27 ` [kernel-hardening] " Kees Cook
2017-06-02 15:20 ` [PATCH 2/6] x86/elf: move 32 bit ELF_ET_DYN_BASE to 256MB riel
2017-06-03 4:22 ` Kees Cook
2017-06-03 11:57 ` Daniel Micay
2017-06-05 13:54 ` Rik van Riel
2017-06-02 15:20 ` [PATCH 3/6] x86/mmap: properly account for stack randomization in mmap_base riel
2017-06-03 4:46 ` [kernel-hardening] " Kees Cook
2017-06-03 12:16 ` Daniel Micay
2017-06-02 15:20 ` [PATCH 4/6] arm64/mmap: " riel
2017-06-02 15:20 ` [PATCH 5/6] arm64: move COMPAT_ELF_ET_DYN_BASE lower in the address space riel
2017-06-02 15:20 ` [PATCH 6/6] powerpc,mmap: properly account for stack randomization in mmap_base riel
2017-06-03 4:37 ` [kernel-hardening] [PATCH 0/6] move mmap_area and PIE binaries away from the stack Kees Cook
2017-06-03 12:14 ` Daniel Micay [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=1496492078.21640.1.camel@gmail.com \
--to=danielmicay@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=benh@kernel.crashing.org \
--cc=keescook@chromium.org \
--cc=kernel-hardening@lists.openwall.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lwoodman@redhat.com \
--cc=mhocko@suse.de \
--cc=mingo@kernel.org \
--cc=oleg@redhat.com \
--cc=riel@redhat.com \
--cc=will.deacon@arm.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).