lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Message-ID: <CAG48ez3-uvDXL7-WBapEJMHrkXYpnAw=AgbP2evOZgNMFWKy-A@mail.gmail.com> Date: Thu, 8 Oct 2020 19:26:31 +0200 From: Jann Horn <jannh@...gle.com> To: Matthew Wilcox <willy@...radead.org> Cc: Topi Miettinen <toiwoton@...il.com>, linux-hardening@...r.kernel.org, Andrew Morton <akpm@...ux-foundation.org>, Linux-MM <linux-mm@...ck.org>, kernel list <linux-kernel@...r.kernel.org> Subject: Re: [PATCH RESEND v2] mm: Optional full ASLR for mmap() and mremap() On Thu, Oct 8, 2020 at 7:23 PM Matthew Wilcox <willy@...radead.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?
Powered by blists - more mailing lists