Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date: Wed, 7 Jun 2017 11:29:32 -0700
From: Kees Cook <>
To: Michael Ellerman <>
Cc: Daniel Micay <>, Bhupesh Sharma <>, 
	"" <>, LKML <>, 
	"" <>, 
	Bhupesh SHARMA <>, Anton Blanchard <>, 
	Daniel Cashman <>, Benjamin Herrenschmidt <>
Subject: Re: [PATCH] powerpc: Increase ELF_ET_DYN_BASE to
 1TB for 64-bit applications

On Wed, Jun 7, 2017 at 2:29 AM, Michael Ellerman <> wrote:
> Daniel Micay <> 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?

I talk a bit about the situation here:

> Is the PaX code somewhere I can look at?

It's near here:

(Note the "&& elf_interpreter" part.) It's replacing the
arch_rnd_mmap() result with its own under some situations, etc.

To do something like this in upstream, we need to be sure we've sanely
dealt with the brk region, which follows the first loaded ELF, and if
it's the interpreter, that means brk ends up in mmap area, up near the
executable area (near what would become the misnomer of


Kees Cook
Pixel Security

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.