From: Luca Barbato <lu_zero@gentoo.org>
To: musl@lists.openwall.com
Subject: Re: Removing sbrk and brk
Date: Sun, 22 Dec 2013 03:15:24 +0100 [thread overview]
Message-ID: <52B64B3C.6090909@gentoo.org> (raw)
In-Reply-To: <20131221234041.GA13204@brightrain.aerifal.cx>
On 22/12/13 00:40, Rich Felker wrote:
> Finally, another alternative might be leaving sbrk/brk alone and
> modifying malloc not to use the brk at all. This has been proposed
> several times (well, supporting non-brk allocation has been proposed
> anyway) to avoid spurious malloc failures when the brk cannot be
> extended, and if we support that we might as well just drop brk
> support in malloc (otherwise there's code with duplicate functionality
> and thus more bloat). So this might actually be the best long-term
> option. Switching malloc from using brk to PROT_NONE/mprotect (see the
> above idea for brk emulation) would also make the malloc
> implementation more portable to systems with no concept of brk.
> However this option would definitely be a post-1.0 development
> direction, and not something we could do right away (of course I'd
> probably hold off until after 1.0 for any of these changes since
> they're fairly invasive, except possibly the idea of making sbrk
> always-fail).
I'd add compile time and runtime warnings and plan for post-1.0
lu
next prev parent reply other threads:[~2013-12-22 2:15 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-21 23:40 Rich Felker
2013-12-22 2:15 ` Luca Barbato [this message]
2013-12-22 17:58 ` Richard Pennington
2013-12-22 18:21 ` Luca Barbato
2013-12-22 18:48 ` Szabolcs Nagy
2013-12-22 21:55 ` Christian Neukirchen
2013-12-23 4:46 ` Rich Felker
2014-01-02 22:03 ` Rich Felker
2014-01-03 11:51 ` Thorsten Glaser
2014-01-03 12:59 ` Daniel Cegiełka
2014-01-03 17:33 ` Rich Felker
2014-01-03 18:19 ` Rich Felker
2014-01-03 19:03 ` Rich Felker
2014-01-06 14:51 ` Thorsten Glaser
2014-01-06 22:40 ` Rich Felker
2014-01-07 9:43 ` Thorsten Glaser
2014-01-07 16:06 ` Rich Felker
2014-01-07 22:00 ` Rich Felker
2014-02-21 16:03 ` Daniel Cegiełka
2014-02-21 16:36 ` Szabolcs Nagy
2014-02-21 16:47 ` Daniel Cegiełka
2014-02-21 17:09 ` Rich Felker
2014-02-21 22:34 ` Daniel Cegiełka
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=52B64B3C.6090909@gentoo.org \
--to=lu_zero@gentoo.org \
--cc=musl@lists.openwall.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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).