From: Andrew Morton <akpm@linux-foundation.org>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: linux-mm@kvack.org
Subject: Re: [PATCH] Bump vm.mmap_min_addr on 64-bit
Date: Mon, 1 Apr 2019 16:05:59 -0700 [thread overview]
Message-ID: <20190401160559.6e945d8d235ae16006702bfc@linux-foundation.org> (raw)
In-Reply-To: <20190401050613.GA16287@avx2>
On Mon, 1 Apr 2019 08:06:13 +0300 Alexey Dobriyan <adobriyan@gmail.com> wrote:
> No self respecting 64-bit program should ever touch that lowly 32-bit
> part of address space.
>
> ...
>
> --- a/mm/Kconfig
> +++ b/mm/Kconfig
> @@ -306,7 +306,8 @@ config KSM
> config DEFAULT_MMAP_MIN_ADDR
> int "Low address space to protect from user allocation"
> depends on MMU
> - default 4096
> + default 4096 if !64BIT
> + default 4294967296 if 64BIT
> help
> This is the portion of low virtual memory which should be protected
> from userspace allocation. Keeping a user from writing to low pages
> --- a/security/Kconfig
> +++ b/security/Kconfig
> @@ -129,7 +129,8 @@ config LSM_MMAP_MIN_ADDR
> int "Low address space for LSM to protect from user allocation"
> depends on SECURITY && SECURITY_SELINUX
> default 32768 if ARM || (ARM64 && COMPAT)
> - default 65536
> + default 65536 if !64BIT
> + default 4294967296 if 64BIT
> help
> This is the portion of low virtual memory which should be protected
> from userspace allocation. Keeping a user from writing to low pages
Gee. Do we have any idea what effect this will have upon all userspace
programs, some of which do inexplicably weird things?
What's the benefit?
next prev parent reply other threads:[~2019-04-01 23:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-01 5:06 Alexey Dobriyan
2019-04-01 23:05 ` Andrew Morton [this message]
2019-04-02 5:57 ` Alexey Dobriyan
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=20190401160559.6e945d8d235ae16006702bfc@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=adobriyan@gmail.com \
--cc=linux-mm@kvack.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