linux-kernel - RE: [PATCH] mm: optionally disable brk()

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Fri, 2 Oct 2020 21:19:33 +0000
From:   David Laight <David.Laight@...LAB.COM>
To:     'David Hildenbrand' <david@...hat.com>,
        Topi Miettinen <toiwoton@...il.com>,
        "akpm@...ux-foundation.org" <akpm@...ux-foundation.org>,
        "linux-mm@...ck.org" <linux-mm@...ck.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH] mm: optionally disable brk()

From: David Hildenbrand
> Sent: 02 October 2020 18:52
> 
> On 02.10.20 19:19, Topi Miettinen wrote:
> > The brk() system call allows to change data segment size (heap). This
> > is mainly used by glibc for memory allocation, but it can use mmap()
> > and that results in more randomized memory mappings since the heap is
> > always located at fixed offset to program while mmap()ed memory is
> > randomized.
> 
> Want to take more Unix out of Linux?
> 
> Honestly, why care about disabling? User space can happily use mmap() if
> it prefers.

I bet some obscure applications rely on it.

Although hopefully nothing still does heap allocation
by just increasing the VA and calling brk() in response
to SIGSEGV.

	David

-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)