From: riel@redhat.com
To: linux-kernel@vger.kernel.org
Cc: kernel-hardening@lists.openwall.com, akpm@linux-foundation.org,
mingo@kernel.org, oleg@redhat.com, lwoodman@redhat.com,
mhocko@suse.de, danielmicay@gmail.com, will.deacon@arm.com,
benh@kernel.crashing.org
Subject: [kernel-hardening] [PATCH 0/6] move mmap_area and PIE binaries away from the stack
Date: Fri, 2 Jun 2017 11:20:04 -0400 [thread overview]
Message-ID: <20170602152010.2064-1-riel@redhat.com> (raw)
There are a few bugs causing the kernel to sometimes map PIE
binaries and the mmap_area where the stack is supposed to go.
This series fixes them for x86, ARM64, and PPC.
S390 seems to be ok.
If people are fine with this approach, I can work my way
through other architectures, too.
next reply other threads:[~2017-06-02 15:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-02 15:20 riel [this message]
2017-06-02 15:20 ` [kernel-hardening] [PATCH 1/6] binfmt_elf: document load_bias a little bit riel
2017-06-02 19:27 ` Kees Cook
2017-06-02 15:20 ` [kernel-hardening] [PATCH 2/6] x86/elf: move 32 bit ELF_ET_DYN_BASE to 256MB riel
2017-06-03 4:22 ` [kernel-hardening] " Kees Cook
2017-06-03 11:57 ` Daniel Micay
2017-06-05 13:54 ` Rik van Riel
2017-06-02 15:20 ` [kernel-hardening] [PATCH 3/6] x86/mmap: properly account for stack randomization in mmap_base riel
2017-06-03 4:46 ` Kees Cook
2017-06-03 12:16 ` Daniel Micay
2017-06-02 15:20 ` [kernel-hardening] [PATCH 4/6] arm64/mmap: " riel
2017-06-02 15:20 ` [kernel-hardening] [PATCH 5/6] arm64: move COMPAT_ELF_ET_DYN_BASE lower in the address space riel
2017-06-02 15:20 ` [kernel-hardening] [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
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=20170602152010.2064-1-riel@redhat.com \
--to=riel@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=benh@kernel.crashing.org \
--cc=danielmicay@gmail.com \
--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=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).