[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <563A5E27.2060607@android.com>
Date: Wed, 4 Nov 2015 11:36:07 -0800
From: Daniel Cashman <dcashman@...roid.com>
To: "Eric W. Biederman" <ebiederm@...ssion.com>,
Michal Hocko <mhocko@...nel.org>
Cc: linux-kernel@...r.kernel.org, linux@....linux.org.uk,
akpm@...ux-foundation.org, keescook@...omium.org, mingo@...nel.org,
linux-arm-kernel@...ts.infradead.org, corbet@....net,
dzickus@...hat.com, xypron.glpk@....de, jpoimboe@...hat.com,
kirill.shutemov@...ux.intel.com, n-horiguchi@...jp.nec.com,
aarcange@...hat.com, mgorman@...e.de, tglx@...utronix.de,
rientjes@...gle.com, linux-mm@...ck.org, linux-doc@...r.kernel.org,
salyzyn@...roid.com, jeffv@...gle.com, nnk@...gle.com,
dcashman <dcashman@...gle.com>
Subject: Re: [PATCH v2 1/2] mm: mmap: Add new /proc tunable for mmap_base
ASLR.
On 11/4/15 11:21 AM, Eric W. Biederman wrote:
> Michal Hocko <mhocko@...nel.org> writes:
>
>> On Tue 03-11-15 10:10:03, Daniel Cashman wrote:
>> [...]
>>> +This value can be changed after boot using the
>>> +/proc/sys/kernel/mmap_rnd_bits tunable
>>
>> Why is this not sitting in /proc/sys/vm/ where we already have
>> mmap_min_addr. These two sound like they should sit together, no?
>
> Ugh. Yes. Moving that file before it becomes part of the ABI sounds
> like a good idea. Daniel when you get around to v3 please move the
> file.
To answer the first question: it was put there because that's where
randomize_va_space is located, which seemed to me to be the
most-related/similar option. That being said, moving it under vm works
too. Will change for patch-set 3.
Thank You,
Dan
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists