From: Michael Ellerman <mpe@ellerman.id.au>
To: Daniel Micay <danielmicay@gmail.com>,
Bhupesh Sharma <bhsharma@redhat.com>,
linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org,
kernel-hardening@lists.openwall.com
Cc: bhupesh.linux@gmail.com, Anton Blanchard <anton@samba.org>,
Daniel Cashman <dcashman@android.com>,
Kees Cook <keescook@chromium.org>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>
Subject: Re: [kernel-hardening] [PATCH] powerpc: Increase ELF_ET_DYN_BASE to 1TB for 64-bit applications
Date: Wed, 07 Jun 2017 19:29:37 +1000 [thread overview]
Message-ID: <87d1agp2m6.fsf@concordia.ellerman.id.au> (raw)
In-Reply-To: <1496665366.343.1.camel@gmail.com>
Daniel Micay <danielmicay@gmail.com> writes:
> Rather than doing this, the base should just be split for an ELF
> interpreter like PaX.
I don't quite parse that, I think you mean PaX uses a different base for
an ELF interpreter vs a regular ET_DYN?
That would be cool. How do you know that it's an ELF interpreter you're
loading? Is it just something that's PIE but doesn't request an
interpreter?
Is the PaX code somewhere I can look at?
> It makes sense for a standalone executable to be as low in the address
> space as possible.
More or less. There are performance reasons why 1T could be good for us,
but I want to see some performance numbers to justify that change. And
it does mean you have a bit less address space to play with.
cheers
next prev parent reply other threads:[~2017-06-07 9:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-05 6:03 [PATCH] powerpc: Increase ELF_ET_DYN_BASE to 1TB for 64-bit applications Bhupesh Sharma
2017-06-05 12:22 ` [kernel-hardening] " Daniel Micay
2017-06-07 9:29 ` Michael Ellerman [this message]
2017-06-07 10:34 ` Bhupesh SHARMA
2017-06-07 18:29 ` Kees Cook
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=87d1agp2m6.fsf@concordia.ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=anton@samba.org \
--cc=benh@kernel.crashing.org \
--cc=bhsharma@redhat.com \
--cc=bhupesh.linux@gmail.com \
--cc=danielmicay@gmail.com \
--cc=dcashman@android.com \
--cc=keescook@chromium.org \
--cc=kernel-hardening@lists.openwall.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
/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).