lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Fri, 2 Jun 2017 21:37:34 -0700 From: Kees Cook <keescook@...omium.org> To: Rik van Riel <riel@...hat.com>, Andrew Morton <akpm@...ux-foundation.org> Cc: LKML <linux-kernel@...r.kernel.org>, "kernel-hardening@...ts.openwall.com" <kernel-hardening@...ts.openwall.com>, Ingo Molnar <mingo@...nel.org>, Oleg Nesterov <oleg@...hat.com>, Larry Woodman <lwoodman@...hat.com>, mhocko@...e.de, Daniel Micay <danielmicay@...il.com>, Will Deacon <will.deacon@....com>, "benh@...nel.crashing.org" <benh@...nel.crashing.org> Subject: Re: [kernel-hardening] [PATCH 0/6] move mmap_area and PIE binaries away from the stack On Fri, Jun 2, 2017 at 8:20 AM, <riel@...hat.com> wrote: > 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. Andrew, I'd rather the ELF_ET_DYN_BASE changes not be in -mm yet. I think it's the wrong approach. Patch 1 (comment update) is fine. Patches 3 and 4 need some (minor?) adjustments, but the ELF_DYN_BASE patches need much more thought, IMO (I've sent a separate email about those.) And please add me to explicit the Cc list for this series. -Kees -- Kees Cook Pixel Security
Powered by blists - more mailing lists