public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: Balbir Singh <bsingharora@gmail•com>
To: Bhupesh Sharma <bhsharma@redhat•com>
Cc: linuxppc-dev@lists•ozlabs.org,
	kernel-hardening@lists•openwall.com,
	Alistair Popple <alistair@popple•id.au>,
	Anatolij Gustschin <agust@denx•de>,
	keescook@chromium•org, Daniel Cashman <dcashman@android•com>,
	Scott Wood <oss@buserror•net>, Paul Mackerras <paulus@samba•org>,
	dcashman@google•com, bhupesh.linux@gmail•com,
	Alexander Graf <agraf@suse•com>
Subject: Re: [PATCH 0/2] RFC: Adjust powerpc ASLR elf randomness
Date: Thu, 2 Feb 2017 12:14:15 +0530	[thread overview]
Message-ID: <20170202064415.GB5179@localhost.localdomain> (raw)
In-Reply-To: <1486014168-1279-1-git-send-email-bhsharma@redhat.com>

On Thu, Feb 02, 2017 at 11:12:46AM +0530, Bhupesh Sharma wrote:
> This RFC patchset tries to make the powerpc ASLR elf randomness
> implementation similar to other ARCHs (like x86).
> 
> The 1st patch introduces the support of ARCH_MMAP_RND_BITS in powerpc
> mmap implementation to allow a sane balance between increased randomness
> in the mmap address of ASLR elfs and increased address space
> fragmentation.
> 

>From what I see we get 28 bits of entropy right for 64k pages
bits as compared to 14 bits earlier?

> The 2nd patch increases the ELF_ET_DYN_BASE value from the current
> hardcoded value of 0x2000_0000 to something more practical,
> i.e. TASK_SIZE - PAGE_SHIFT (which makes sense especially for
> 64-bit platforms which would like to utilize more randomization
> in the load address of a PIE elf).
> 

This helps PIE executables as such and leaves other not impacted?

Balbir Singh

  parent reply	other threads:[~2017-02-02  6:44 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-02  5:42 [PATCH 0/2] RFC: Adjust powerpc ASLR elf randomness Bhupesh Sharma
2017-02-02  5:42 ` [PATCH 1/2] powerpc: mm: support ARCH_MMAP_RND_BITS Bhupesh Sharma
2017-02-02  9:11   ` Balbir Singh
2017-02-02 18:14     ` Bhupesh Sharma
2017-02-02 10:23   ` Michael Ellerman
2017-02-02 12:22     ` Balbir Singh
2017-02-02 23:59       ` [kernel-hardening] " Michael Ellerman
2017-02-08 12:53     ` Bhupesh Sharma
2017-02-10 11:01       ` [kernel-hardening] " Michael Ellerman
2017-02-10 11:11         ` Bhupesh Sharma
2017-02-16  4:49           ` Bhupesh Sharma
2017-02-24  7:32             ` Bhupesh Sharma
2017-02-24  9:53               ` Michael Ellerman
2017-02-02 14:25   ` Kees Cook
2017-02-02 18:04     ` Bhupesh Sharma
2017-02-02  5:42 ` [PATCH 2/2] powerpc: Redefine ELF_ET_DYN_BASE Bhupesh Sharma
2017-02-02  6:44 ` Balbir Singh [this message]
2017-02-02 18:21   ` [PATCH 0/2] RFC: Adjust powerpc ASLR elf randomness Bhupesh Sharma
2017-02-02 14:21 ` Kees Cook
2017-02-02 18:08   ` Bhupesh Sharma
2017-02-02 19:19     ` Kees Cook
2017-02-02 19:43       ` Bhupesh Sharma

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=20170202064415.GB5179@localhost.localdomain \
    --to=bsingharora@gmail$(echo .)com \
    --cc=agraf@suse$(echo .)com \
    --cc=agust@denx$(echo .)de \
    --cc=alistair@popple$(echo .)id.au \
    --cc=bhsharma@redhat$(echo .)com \
    --cc=bhupesh.linux@gmail$(echo .)com \
    --cc=dcashman@android$(echo .)com \
    --cc=dcashman@google$(echo .)com \
    --cc=keescook@chromium$(echo .)org \
    --cc=kernel-hardening@lists$(echo .)openwall.com \
    --cc=linuxppc-dev@lists$(echo .)ozlabs.org \
    --cc=oss@buserror$(echo .)net \
    --cc=paulus@samba$(echo .)org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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