From: Rik van Riel <riel@redhat.com>
To: Daniel Micay <danielmicay@gmail.com>, Kees Cook <keescook@chromium.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Qualys Security Advisory <qsa@qualys.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
"x86@kernel.org" <x86@kernel.org>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Dmitry Safonov <dsafonov@virtuozzo.com>,
Masahiro Yamada <yamada.masahiro@socionext.com>,
Grzegorz Andrejczuk <grzegorz.andrejczuk@intel.com>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"kernel-hardening@lists.openwall.com"
<kernel-hardening@lists.openwall.com>
Subject: Re: [kernel-hardening] [PATCH] [RFC] binfmt_elf: Use ELF_ET_DYN_BASE only for PIE
Date: Wed, 21 Jun 2017 14:47:49 -0400 [thread overview]
Message-ID: <1498070869.13083.22.camel@redhat.com> (raw)
In-Reply-To: <1498066333.27465.8.camel@gmail.com>
On Wed, 2017-06-21 at 13:32 -0400, Daniel Micay wrote:
> On Wed, 2017-06-21 at 10:28 -0700, Kees Cook wrote:
> > > The stack rlimit calculation fix for space potentially lost to
> > > ASLR
> > > is
> > > probably still needed too, right?
> >
> > Yes. Was that picked up by akpm already?
> >
> > -Kees
>
> I think it was dropped when the ET_DYN changes were dropped.
I can resend those.
prev parent reply other threads:[~2017-06-21 18:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-21 5:58 [kernel-hardening] [PATCH] [RFC] binfmt_elf: Use ELF_ET_DYN_BASE only for PIE Kees Cook
2017-06-21 5:58 ` Kees Cook
2017-06-21 12:07 ` [kernel-hardening] " Rik van Riel
2017-06-21 17:23 ` Kees Cook
2017-06-21 17:27 ` Daniel Micay
2017-06-21 17:28 ` Kees Cook
2017-06-21 17:32 ` Daniel Micay
2017-06-21 17:33 ` Kees Cook
2017-06-21 18:47 ` Rik van Riel [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=1498070869.13083.22.camel@redhat.com \
--to=riel@redhat.com \
--cc=danielmicay@gmail.com \
--cc=dsafonov@virtuozzo.com \
--cc=grzegorz.andrejczuk@intel.com \
--cc=hpa@zytor.com \
--cc=keescook@chromium.org \
--cc=kernel-hardening@lists.openwall.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=qsa@qualys.com \
--cc=tglx@linutronix.de \
--cc=viro@zeniv.linux.org.uk \
--cc=x86@kernel.org \
--cc=yamada.masahiro@socionext.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.