From: Andrew Morton <akpm@linux-foundation.org>
To: Rafael Aquini <aquini@redhat.com>
Cc: linux-kernel@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>,
Heiko Carstens <hca@linux.ibm.com>,
Petr Mladek <pmladek@suse.com>, Mike Rapoport <rppt@kernel.org>,
Paul McKenney <paulmck@kernel.org>,
Samuel Holland <samuel.holland@sifive.com>
Subject: Re: [PATCH v2] mm: mmap: allow for the maximum number of bits for randomizing mmap_base by default
Date: Mon, 10 Jun 2024 11:11:39 -0700 [thread overview]
Message-ID: <20240610111139.1e392360ffe847ea48ffebab@linux-foundation.org> (raw)
In-Reply-To: <20240606180622.102099-1-aquini@redhat.com>
On Thu, 6 Jun 2024 14:06:22 -0400 Rafael Aquini <aquini@redhat.com> wrote:
> An ASLR regression was noticed [1] and tracked down to file-mapped areas
> being backed by THP in recent kernels. The 21-bit alignment constraint
> for such mappings reduces the entropy for randomizing the placement of
> 64-bit library mappings and breaks ASLR completely for 32-bit libraries.
>
> The reported issue is easily addressed by increasing vm.mmap_rnd_bits
> and vm.mmap_rnd_compat_bits. This patch just provides a simple way to
> set ARCH_MMAP_RND_BITS and ARCH_MMAP_RND_COMPAT_BITS to their maximum
> values allowed by the architecture at build time.
>
> [1] https://zolutal.github.io/aslrnt/
Are we able to identify a Fixes: target for this?
I assume a cc:stable is appropriate?
next prev parent reply other threads:[~2024-06-10 18:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-06 17:00 [PATCH] " Rafael Aquini
2024-06-06 18:06 ` [PATCH v2] " Rafael Aquini
2024-06-10 18:11 ` Andrew Morton [this message]
2024-06-10 18:45 ` Rafael Aquini
2024-06-11 21:32 ` Andrew Morton
2024-06-12 1:35 ` Rafael Aquini
2024-06-12 2:43 ` Andrew Morton
2024-06-12 12:26 ` Rafael Aquini
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=20240610111139.1e392360ffe847ea48ffebab@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=aquini@redhat.com \
--cc=arnd@arndb.de \
--cc=hca@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@kernel.org \
--cc=pmladek@suse.com \
--cc=rppt@kernel.org \
--cc=samuel.holland@sifive.com \
/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
all inboxes | Powered by JetHome®