From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v6 3/4] arm64: mm: support ARCH_MMAP_RND_BITS.
Date: Mon, 14 Dec 2015 11:19:49 +0000 [thread overview]
Message-ID: <20151214111949.GD6992@arm.com> (raw)
In-Reply-To: <1449856338-30984-4-git-send-email-dcashman@android.com>
Hi Daniel,
On Fri, Dec 11, 2015 at 09:52:17AM -0800, Daniel Cashman wrote:
> From: dcashman <dcashman@google.com>
>
> arm64: arch_mmap_rnd() uses STACK_RND_MASK to generate the
> random offset for the mmap base address. This value represents a
> compromise between increased ASLR effectiveness and avoiding
> address-space fragmentation. Replace it with a Kconfig option, which
> is sensibly bounded, so that platform developers may choose where to
> place this compromise. Keep default values as new minimums.
>
> Signed-off-by: Daniel Cashman <dcashman@android.com>
> ---
> arch/arm64/Kconfig | 33 +++++++++++++++++++++++++++++++++
> arch/arm64/mm/mmap.c | 8 ++++++--
> 2 files changed, 39 insertions(+), 2 deletions(-)
>
> diff --git a/arch/arm64/Kconfig b/arch/arm64/Kconfig
> index 871f217..0cc9c24 100644
> --- a/arch/arm64/Kconfig
> +++ b/arch/arm64/Kconfig
> @@ -51,6 +51,8 @@ config ARM64
> select HAVE_ARCH_JUMP_LABEL
> select HAVE_ARCH_KASAN if SPARSEMEM_VMEMMAP && !(ARM64_16K_PAGES && ARM64_VA_BITS_48)
> select HAVE_ARCH_KGDB
> + select HAVE_ARCH_MMAP_RND_BITS
> + select HAVE_ARCH_MMAP_RND_COMPAT_BITS if COMPAT
> select HAVE_ARCH_SECCOMP_FILTER
> select HAVE_ARCH_TRACEHOOK
> select HAVE_BPF_JIT
> @@ -104,6 +106,37 @@ config ARCH_PHYS_ADDR_T_64BIT
> config MMU
> def_bool y
>
> +config ARCH_MMAP_RND_BITS_MIN
> + default 14 if ARM64_64K_PAGES
> + default 16 if ARM64_16K_PAGES
> + default 18
> +
> +# max bits determined by the following formula:
> +# VA_BITS - PAGE_SHIFT - 3
Now that we have this comment, I think we can drop the unsupported
combinations from the list below. That means we just end up with:
> +config ARCH_MMAP_RND_BITS_MAX
> + default 19 if ARM64_VA_BITS=36
> + default 24 if ARM64_VA_BITS=39
> + default 27 if ARM64_VA_BITS=42
> + default 30 if ARM64_VA_BITS=47
> + default 29 if ARM64_VA_BITS=48 && ARM64_64K_PAGES
> + default 31 if ARM64_VA_BITS=48 && ARM64_16K_PAGES
> + default 33 if ARM64_VA_BITS=48
With that:
Acked-by: Will Deacon <will.deacon@arm.com>
Will
next prev parent reply other threads:[~2015-12-14 11:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-11 17:52 [PATCH v6 0/4] Allow customizable random offset to mmap_base address Daniel Cashman
2015-12-11 17:52 ` [PATCH v6 1/4] mm: mmap: Add new /proc tunable for mmap_base ASLR Daniel Cashman
2015-12-11 17:52 ` [PATCH v6 2/4] arm: mm: support ARCH_MMAP_RND_BITS Daniel Cashman
2015-12-11 17:52 ` [PATCH v6 3/4] arm64: " Daniel Cashman
2015-12-11 17:52 ` [PATCH v6 4/4] x86: " Daniel Cashman
2015-12-14 18:58 ` H. Peter Anvin
2015-12-14 20:51 ` Daniel Cashman
2015-12-14 11:19 ` Will Deacon [this message]
2015-12-14 20:45 ` [PATCH v6 3/4] arm64: " Daniel Cashman
2015-12-11 21:02 ` [PATCH v6 0/4] Allow customizable random offset to mmap_base address 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=20151214111949.GD6992@arm.com \
--to=will.deacon@arm.com \
--cc=linux-arm-kernel@lists.infradead.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).