On Mon, Jun 26, 2017 at 6:04 AM, Michael Ellerman wrote:
> Kees Cook writes:
>
>> On Fri, Jun 23, 2017 at 12:01 AM, Michael Ellerman
>> wrote:
>>> Kees Cook writes:
>>>
Now that explicitly executed loaders are loaded in the mmap region,
position PIE binaries lower in the address spac
Kees Cook writes:
> On Fri, Jun 23, 2017 at 12:01 AM, Michael Ellerman
> wrote:
>> Kees Cook writes:
>>
>>> Now that explicitly executed loaders are loaded in the mmap region,
>>> position PIE binaries lower in the address space to avoid possible
>>> collisions with mmap or stack regions. For
On Fri, Jun 23, 2017 at 12:01 AM, Michael Ellerman wrote:
> Kees Cook writes:
>
>> Now that explicitly executed loaders are loaded in the mmap region,
>> position PIE binaries lower in the address space to avoid possible
>> collisions with mmap or stack regions. For 64-bit, align to 4GB to
>> all
Kees Cook writes:
> Now that explicitly executed loaders are loaded in the mmap region,
> position PIE binaries lower in the address space to avoid possible
> collisions with mmap or stack regions. For 64-bit, align to 4GB to
> allow runtimes to use the entire 32-bit address space for 32-bit
> po
Now that explicitly executed loaders are loaded in the mmap region,
position PIE binaries lower in the address space to avoid possible
collisions with mmap or stack regions. For 64-bit, align to 4GB to
allow runtimes to use the entire 32-bit address space for 32-bit
pointers.
Signed-off-by: Kees C
