[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87d1agp2m6.fsf@concordia.ellerman.id.au>
Date: Wed, 07 Jun 2017 19:29:37 +1000
From: Michael Ellerman <mpe@...erman.id.au>
To: Daniel Micay <danielmicay@...il.com>, Bhupesh Sharma <bhsharma@...hat.com>, linuxppc-dev@...ts.ozlabs.org, linux-kernel@...r.kernel.org, kernel-hardening@...ts.openwall.com
Cc: bhupesh.linux@...il.com, Anton Blanchard <anton@...ba.org>, Daniel Cashman <dcashman@...roid.com>, Kees Cook <keescook@...omium.org>, Benjamin Herrenschmidt <benh@...nel.crashing.org>
Subject: Re: [PATCH] powerpc: Increase ELF_ET_DYN_BASE to 1TB for 64-bit applications
Daniel Micay <danielmicay@...il.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
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
