From: Jann Horn <jannh@google.com>
To: Matthew Wilcox <willy@infradead.org>
Cc: Topi Miettinen <toiwoton@gmail.com>,
linux-hardening@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Linux-MM <linux-mm@kvack.org>,
kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH RESEND v2] mm: Optional full ASLR for mmap() and mremap()
Date: Thu, 8 Oct 2020 19:26:31 +0200 [thread overview]
Message-ID: <CAG48ez3-uvDXL7-WBapEJMHrkXYpnAw=AgbP2evOZgNMFWKy-A@mail.gmail.com> (raw)
In-Reply-To: <20201008172300.GL20115@casper.infradead.org>
On Thu, Oct 8, 2020 at 7:23 PM Matthew Wilcox <willy@infradead.org> wrote:
> On Thu, Oct 08, 2020 at 07:13:51PM +0200, Jann Horn wrote:
> > And for expanding stacks, it might be a good idea for other
> > reasons as well (locking consistency) to refactor them such that the
> > size in the VMA tree corresponds to the maximum expansion of the stack
> > (and if an allocation is about to fail, shrink such stack mappings).
>
> We're doing that as part of the B-tree ;-) Although not the shrink
> stack mappings part ...
Wheee, thanks! Finally no more data races on ->vm_start?
next prev parent reply other threads:[~2020-10-08 17:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-08 16:54 [PATCH RESEND v2] mm: Optional full ASLR for mmap() and mremap() Topi Miettinen
2020-10-08 17:07 ` Matthew Wilcox
2020-10-08 18:11 ` Topi Miettinen
2020-10-08 17:13 ` Jann Horn
2020-10-08 17:23 ` Matthew Wilcox
2020-10-08 17:26 ` Jann Horn [this message]
2020-10-08 17:41 ` Matthew Wilcox
2020-10-08 18:10 ` Topi Miettinen
2020-10-08 18:24 ` Jann Horn
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='CAG48ez3-uvDXL7-WBapEJMHrkXYpnAw=AgbP2evOZgNMFWKy-A@mail.gmail.com' \
--to=jannh@google.com \
--cc=akpm@linux-foundation.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=toiwoton@gmail.com \
--cc=willy@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).