mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Re: New malloc - first preview
Date: Fri, 29 Nov 2019 23:49:26 -0500	[thread overview]
Message-ID: <20191130044926.GR16318@brightrain.aerifal.cx> (raw)
In-Reply-To: <CADA+G1vkDUdFe7H+eGP+p2cmW41_M8L_d7219pXnoCm0dWZu9A@mail.gmail.com>

On Fri, Nov 29, 2019 at 06:41:08PM +0200, Roman Yeryomin wrote:
> On Thu, Nov 28, 2019 at 11:56 PM Rich Felker <dalias@libc.org> wrote:
> >
> > Work on the new malloc is well underway, and I have a draft version
> > now public at:
> >
> > https://github.com/richfelker/mallocng-draft
> 
> Hi Rich,
> will it cover this problem: https://www.openwall.com/lists/musl/2018/02/09/4 ?

Yes. This is the main initial motivation for redoing malloc. I haven't
run that specific test case, but I have one which should be roughly
equivalent and it passes fine (no exploding heap usage).

Rich


  reply	other threads:[~2019-11-30  4:49 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-22 17:40 New malloc - intro, motivation & design goals document Rich Felker
2019-11-06  3:46 ` Non-candidate allocator designs, things to learn from them Rich Felker
2019-11-06 10:06   ` Florian Weimer
2019-11-28 21:56 ` New malloc - first preview Rich Felker
2019-11-28 22:22   ` Rich Felker
2019-11-29  6:37     ` Vasya Boytsov
2019-11-29 13:55       ` Rich Felker
2019-11-30  5:54         ` Rich Felker
2019-11-29 16:41   ` Roman Yeryomin
2019-11-30  4:49     ` Rich Felker [this message]
2019-11-29 19:45   ` Markus Wichmann
2019-11-30  3:15     ` Rich Felker
2019-11-30 22:11   ` Rich Felker
2019-12-06  5:06     ` Rich Felker

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=20191130044926.GR16318@brightrain.aerifal.cx \
    --to=dalias@libc.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).