[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Dumper problems and a possible solutions

From: Samuel Bronson
Subject: Re: Dumper problems and a possible solutions
Date: Wed, 25 Jun 2014 16:53:58 -0400

On 6/25/14, Rich Felker <address@hidden> wrote:

> In musl's malloc, we use brk if it's available (note: with PIE, most
> kernels give you almost no available brk space due to the way the
> mappings are laid out) [...]

Yeah, that tiny gap has bitten in other ways, too:
talks about a stack overflow with the same cause; I really think the
kernel should stop doing that.

> Also, musl does not provide a working sbrk at all, since synchronizing
> with an application's use of sbrk would introduce performance costs
> into all correct applications that don't poke at the brk.

Looking at the manpage, I can't really follow how having sbrk() would
involve a slowdown in everything?  Do you mean that musl's malloc gets
a speed bonus out of assuming it's the sole user of brk()/sbrk(), and
thus the whole region from the initial brk()point to the current
brk()point is belongs to it?  (Yeah, all (potentially) 125 MiB -
stacksize of it!)

reply via email to

[Prev in Thread] Current Thread [Next in Thread]