From: dcashman@android.com (Daniel Cashman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 1/4] mm: mmap: Add new /proc tunable for mmap_base ASLR.
Date: Wed, 25 Nov 2015 11:36:42 -0800 [thread overview]
Message-ID: <56560DCA.7050009@android.com> (raw)
In-Reply-To: <1448426400.3762.11.camel@ellerman.id.au>
On 11/24/2015 08:40 PM, Michael Ellerman wrote:
> On Wed, 2015-11-18 at 15:20 -0800, Daniel Cashman wrote:
>
>> From: dcashman <dcashman@google.com>
>>
>> ASLR currently only uses 8 bits to generate the random offset for the
>> mmap base address on 32 bit architectures. This value was chosen to
>> prevent a poorly chosen value from dividing the address space in such
>> a way as to prevent large allocations. This may not be an issue on all
>> platforms. Allow the specification of a minimum number of bits so that
>> platforms desiring greater ASLR protection may determine where to place
>> the trade-off.
>
> ...
>
>> diff --git a/arch/Kconfig b/arch/Kconfig
>> index 4e949e5..141823f 100644
>> --- a/arch/Kconfig
>> +++ b/arch/Kconfig
>> @@ -511,6 +511,70 @@ config ARCH_HAS_ELF_RANDOMIZE
>> - arch_mmap_rnd()
>> - arch_randomize_brk()
>>
>> +config HAVE_ARCH_MMAP_RND_BITS
>> + bool
>> + help
>> + An arch should select this symbol if it supports setting a variable
>> + number of bits for use in establishing the base address for mmap
>> + allocations and provides values for both:
>> + - ARCH_MMAP_RND_BITS_MIN
>> + - ARCH_MMAP_RND_BITS_MAX
>> +
>> +config ARCH_MMAP_RND_BITS_MIN
>> + int
>> +
>> +config ARCH_MMAP_RND_BITS_MAX
>> + int
>> +
>> +config ARCH_MMAP_RND_BITS_DEFAULT
>> + int
>> +
>> +config ARCH_MMAP_RND_BITS
>> + int "Number of bits to use for ASLR of mmap base address" if EXPERT
>> + range ARCH_MMAP_RND_BITS_MIN ARCH_MMAP_RND_BITS_MAX
>> + default ARCH_MMAP_RND_BITS_DEFAULT if ARCH_MMAP_RND_BITS_DEFAULT
>
> Here you support a default which is separate from the minimum.
>
>> + default ARCH_MMAP_RND_BITS_MIN
>> + depends on HAVE_ARCH_MMAP_RND_BITS
>
> ...
>> +
>> +config ARCH_MMAP_RND_COMPAT_BITS
>> + int "Number of bits to use for ASLR of mmap base address for compatible applications" if EXPERT
>> + range ARCH_MMAP_RND_COMPAT_BITS_MIN ARCH_MMAP_RND_COMPAT_BITS_MAX
>> + default ARCH_MMAP_RND_COMPAT_BITS_MIN
>
> But here you don't.
>
> Just forgot?
Yes. Good catch.
> I'd like to have a default which is separate from the minimum. That way we can
> have a default which is reasonably large, but allow it to be lowered easily if
> anything breaks.
Will add it, along w/the documentation cleanup and other changes.
Thank You,
Dan
WARNING: multiple messages have this Message-ID (diff)
From: Daniel Cashman <dcashman@android.com>
To: Michael Ellerman <mpe@ellerman.id.au>, linux-kernel@vger.kernel.org
Cc: linux@arm.linux.org.uk, akpm@linux-foundation.org,
keescook@chromium.org, mingo@kernel.org,
linux-arm-kernel@lists.infradead.org, corbet@lwn.net,
dzickus@redhat.com, ebiederm@xmission.com, xypron.glpk@gmx.de,
jpoimboe@redhat.com, kirill.shutemov@linux.intel.com,
n-horiguchi@ah.jp.nec.com, aarcange@redhat.com, mgorman@suse.de,
tglx@linutronix.de, rientjes@google.com, linux-mm@kvack.org,
linux-doc@vger.kernel.org, salyzyn@android.com, jeffv@google.com,
nnk@google.com, catalin.marinas@arm.com, will.deacon@arm.com,
hpa@zytor.com, x86@kernel.org, hecmargi@upv.es, bp@suse.de,
dcashman@google.com
Subject: Re: [PATCH v3 1/4] mm: mmap: Add new /proc tunable for mmap_base ASLR.
Date: Wed, 25 Nov 2015 11:36:42 -0800 [thread overview]
Message-ID: <56560DCA.7050009@android.com> (raw)
In-Reply-To: <1448426400.3762.11.camel@ellerman.id.au>
On 11/24/2015 08:40 PM, Michael Ellerman wrote:
> On Wed, 2015-11-18 at 15:20 -0800, Daniel Cashman wrote:
>
>> From: dcashman <dcashman@google.com>
>>
>> ASLR currently only uses 8 bits to generate the random offset for the
>> mmap base address on 32 bit architectures. This value was chosen to
>> prevent a poorly chosen value from dividing the address space in such
>> a way as to prevent large allocations. This may not be an issue on all
>> platforms. Allow the specification of a minimum number of bits so that
>> platforms desiring greater ASLR protection may determine where to place
>> the trade-off.
>
> ...
>
>> diff --git a/arch/Kconfig b/arch/Kconfig
>> index 4e949e5..141823f 100644
>> --- a/arch/Kconfig
>> +++ b/arch/Kconfig
>> @@ -511,6 +511,70 @@ config ARCH_HAS_ELF_RANDOMIZE
>> - arch_mmap_rnd()
>> - arch_randomize_brk()
>>
>> +config HAVE_ARCH_MMAP_RND_BITS
>> + bool
>> + help
>> + An arch should select this symbol if it supports setting a variable
>> + number of bits for use in establishing the base address for mmap
>> + allocations and provides values for both:
>> + - ARCH_MMAP_RND_BITS_MIN
>> + - ARCH_MMAP_RND_BITS_MAX
>> +
>> +config ARCH_MMAP_RND_BITS_MIN
>> + int
>> +
>> +config ARCH_MMAP_RND_BITS_MAX
>> + int
>> +
>> +config ARCH_MMAP_RND_BITS_DEFAULT
>> + int
>> +
>> +config ARCH_MMAP_RND_BITS
>> + int "Number of bits to use for ASLR of mmap base address" if EXPERT
>> + range ARCH_MMAP_RND_BITS_MIN ARCH_MMAP_RND_BITS_MAX
>> + default ARCH_MMAP_RND_BITS_DEFAULT if ARCH_MMAP_RND_BITS_DEFAULT
>
> Here you support a default which is separate from the minimum.
>
>> + default ARCH_MMAP_RND_BITS_MIN
>> + depends on HAVE_ARCH_MMAP_RND_BITS
>
> ...
>> +
>> +config ARCH_MMAP_RND_COMPAT_BITS
>> + int "Number of bits to use for ASLR of mmap base address for compatible applications" if EXPERT
>> + range ARCH_MMAP_RND_COMPAT_BITS_MIN ARCH_MMAP_RND_COMPAT_BITS_MAX
>> + default ARCH_MMAP_RND_COMPAT_BITS_MIN
>
> But here you don't.
>
> Just forgot?
Yes. Good catch.
> I'd like to have a default which is separate from the minimum. That way we can
> have a default which is reasonably large, but allow it to be lowered easily if
> anything breaks.
Will add it, along w/the documentation cleanup and other changes.
Thank You,
Dan
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
WARNING: multiple messages have this Message-ID (diff)
From: Daniel Cashman <dcashman@android.com>
To: Michael Ellerman <mpe@ellerman.id.au>, linux-kernel@vger.kernel.org
Cc: linux@arm.linux.org.uk, akpm@linux-foundation.org,
keescook@chromium.org, mingo@kernel.org,
linux-arm-kernel@lists.infradead.org, corbet@lwn.net,
dzickus@redhat.com, ebiederm@xmission.com, xypron.glpk@gmx.de,
jpoimboe@redhat.com, kirill.shutemov@linux.intel.com,
n-horiguchi@ah.jp.nec.com, aarcange@redhat.com, mgorman@suse.de,
tglx@linutronix.de, rientjes@google.com, linux-mm@kvack.org,
linux-doc@vger.kernel.org, salyzyn@android.com, jeffv@google.com,
nnk@google.com, catalin.marinas@arm.com, will.deacon@arm.com,
hpa@zytor.com, x86@kernel.org, hecmargi@upv.es, bp@suse.de,
dcashman@google.com
Subject: Re: [PATCH v3 1/4] mm: mmap: Add new /proc tunable for mmap_base ASLR.
Date: Wed, 25 Nov 2015 11:36:42 -0800 [thread overview]
Message-ID: <56560DCA.7050009@android.com> (raw)
In-Reply-To: <1448426400.3762.11.camel@ellerman.id.au>
On 11/24/2015 08:40 PM, Michael Ellerman wrote:
> On Wed, 2015-11-18 at 15:20 -0800, Daniel Cashman wrote:
>
>> From: dcashman <dcashman@google.com>
>>
>> ASLR currently only uses 8 bits to generate the random offset for the
>> mmap base address on 32 bit architectures. This value was chosen to
>> prevent a poorly chosen value from dividing the address space in such
>> a way as to prevent large allocations. This may not be an issue on all
>> platforms. Allow the specification of a minimum number of bits so that
>> platforms desiring greater ASLR protection may determine where to place
>> the trade-off.
>
> ...
>
>> diff --git a/arch/Kconfig b/arch/Kconfig
>> index 4e949e5..141823f 100644
>> --- a/arch/Kconfig
>> +++ b/arch/Kconfig
>> @@ -511,6 +511,70 @@ config ARCH_HAS_ELF_RANDOMIZE
>> - arch_mmap_rnd()
>> - arch_randomize_brk()
>>
>> +config HAVE_ARCH_MMAP_RND_BITS
>> + bool
>> + help
>> + An arch should select this symbol if it supports setting a variable
>> + number of bits for use in establishing the base address for mmap
>> + allocations and provides values for both:
>> + - ARCH_MMAP_RND_BITS_MIN
>> + - ARCH_MMAP_RND_BITS_MAX
>> +
>> +config ARCH_MMAP_RND_BITS_MIN
>> + int
>> +
>> +config ARCH_MMAP_RND_BITS_MAX
>> + int
>> +
>> +config ARCH_MMAP_RND_BITS_DEFAULT
>> + int
>> +
>> +config ARCH_MMAP_RND_BITS
>> + int "Number of bits to use for ASLR of mmap base address" if EXPERT
>> + range ARCH_MMAP_RND_BITS_MIN ARCH_MMAP_RND_BITS_MAX
>> + default ARCH_MMAP_RND_BITS_DEFAULT if ARCH_MMAP_RND_BITS_DEFAULT
>
> Here you support a default which is separate from the minimum.
>
>> + default ARCH_MMAP_RND_BITS_MIN
>> + depends on HAVE_ARCH_MMAP_RND_BITS
>
> ...
>> +
>> +config ARCH_MMAP_RND_COMPAT_BITS
>> + int "Number of bits to use for ASLR of mmap base address for compatible applications" if EXPERT
>> + range ARCH_MMAP_RND_COMPAT_BITS_MIN ARCH_MMAP_RND_COMPAT_BITS_MAX
>> + default ARCH_MMAP_RND_COMPAT_BITS_MIN
>
> But here you don't.
>
> Just forgot?
Yes. Good catch.
> I'd like to have a default which is separate from the minimum. That way we can
> have a default which is reasonably large, but allow it to be lowered easily if
> anything breaks.
Will add it, along w/the documentation cleanup and other changes.
Thank You,
Dan
next prev parent reply other threads:[~2015-11-25 19:36 UTC|newest]
Thread overview: 72+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-18 23:20 [PATCH v3 0/4] Allow customizable random offset to mmap_base address Daniel Cashman
2015-11-18 23:20 ` Daniel Cashman
2015-11-18 23:20 ` Daniel Cashman
2015-11-18 23:20 ` [PATCH v3 1/4] mm: mmap: Add new /proc tunable for mmap_base ASLR Daniel Cashman
2015-11-18 23:20 ` Daniel Cashman
2015-11-18 23:20 ` Daniel Cashman
2015-11-18 23:20 ` [PATCH v3 2/4] arm: mm: support ARCH_MMAP_RND_BITS Daniel Cashman
2015-11-18 23:20 ` Daniel Cashman
2015-11-18 23:20 ` Daniel Cashman
2015-11-18 23:20 ` [PATCH v3 3/4] arm64: " Daniel Cashman
2015-11-18 23:20 ` Daniel Cashman
2015-11-18 23:20 ` Daniel Cashman
2015-11-18 23:20 ` [PATCH v3 4/4] x86: " Daniel Cashman
2015-11-18 23:20 ` Daniel Cashman
2015-11-18 23:20 ` Daniel Cashman
2015-11-19 0:16 ` Daniel Cashman
2015-11-19 0:16 ` Daniel Cashman
2015-11-19 0:16 ` Daniel Cashman
2015-11-23 15:04 ` [PATCH v3 3/4] arm64: " Will Deacon
2015-11-23 15:04 ` Will Deacon
2015-11-23 15:04 ` Will Deacon
2015-11-23 18:55 ` Daniel Cashman
2015-11-23 18:55 ` Daniel Cashman
2015-11-23 18:55 ` Daniel Cashman
2015-11-25 4:26 ` Michael Ellerman
2015-11-25 4:26 ` Michael Ellerman
2015-11-25 4:26 ` Michael Ellerman
2015-11-25 19:32 ` Daniel Cashman
2015-11-25 19:32 ` Daniel Cashman
2015-11-25 19:32 ` Daniel Cashman
2015-11-25 12:06 ` Catalin Marinas
2015-11-25 12:06 ` Catalin Marinas
2015-11-25 12:06 ` Catalin Marinas
2015-11-25 20:39 ` Daniel Cashman
2015-11-25 20:39 ` Daniel Cashman
2015-11-25 20:39 ` Daniel Cashman
2015-11-27 8:36 ` Andrey Ryabinin
2015-11-27 8:36 ` Andrey Ryabinin
2015-11-27 8:36 ` Andrey Ryabinin
2015-11-27 9:32 ` Catalin Marinas
2015-11-27 9:32 ` Catalin Marinas
2015-11-27 9:32 ` Catalin Marinas
2015-11-19 0:14 ` [PATCH v3 1/4] mm: mmap: Add new /proc tunable for mmap_base ASLR Daniel Cashman
2015-11-19 0:14 ` Daniel Cashman
2015-11-19 0:14 ` Daniel Cashman
2015-11-25 0:40 ` Andrew Morton
2015-11-25 0:40 ` Andrew Morton
2015-11-25 0:40 ` Andrew Morton
2015-11-25 0:47 ` Kees Cook
2015-11-25 0:47 ` Kees Cook
2015-11-25 0:47 ` Kees Cook
2015-11-25 19:16 ` Daniel Cashman
2015-11-25 19:16 ` Daniel Cashman
2015-11-25 19:16 ` Daniel Cashman
2015-11-25 4:40 ` Michael Ellerman
2015-11-25 4:40 ` Michael Ellerman
2015-11-25 4:40 ` Michael Ellerman
2015-11-25 19:36 ` Daniel Cashman [this message]
2015-11-25 19:36 ` Daniel Cashman
2015-11-25 19:36 ` Daniel Cashman
2015-11-25 0:39 ` [PATCH v3 0/4] Allow customizable random offset to mmap_base address Andrew Morton
2015-11-25 0:39 ` Andrew Morton
2015-11-25 0:39 ` Andrew Morton
2015-11-25 19:07 ` Daniel Cashman
2015-11-25 19:07 ` Daniel Cashman
2015-11-25 19:07 ` Daniel Cashman
2015-11-26 15:11 ` Martin Schwidefsky
2015-11-26 15:11 ` Martin Schwidefsky
2015-11-26 15:11 ` Martin Schwidefsky
2015-11-26 7:07 ` Michael Ellerman
2015-11-26 7:07 ` Michael Ellerman
2015-11-26 7:07 ` Michael Ellerman
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=56560DCA.7050009@android.com \
--to=dcashman@android.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.