From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-3.3 required=5.0 tests=MAILING_LIST_MULTI, RCVD_IN_DNSWL_MED,RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 25699 invoked from network); 11 Jun 2020 03:49:53 -0000 Received: from mother.openwall.net (195.42.179.200) by inbox.vuxu.org with ESMTPUTF8; 11 Jun 2020 03:49:53 -0000 Received: (qmail 20078 invoked by uid 550); 11 Jun 2020 03:49:48 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-ID: Reply-To: musl@lists.openwall.com Received: (qmail 20057 invoked from network); 11 Jun 2020 03:49:47 -0000 Date: Wed, 10 Jun 2020 23:49:34 -0400 From: Rich Felker To: musl@lists.openwall.com Message-ID: <20200611034934.GL1079@brightrain.aerifal.cx> References: <20200609035010.GE1079@brightrain.aerifal.cx> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20200609035010.GE1079@brightrain.aerifal.cx> User-Agent: Mutt/1.5.21 (2010-09-15) Subject: Re: [musl] mallocng switchover - opportunity to test On Mon, Jun 08, 2020 at 11:50:10PM -0400, Rich Felker wrote: > I just pushed a series of changes in preparation for upstreaming > mallocng. Before it's actually imported, it can be tested by > performing the following simple 4 steps: > > 1. mkdir src/malloc/mallocng > 2. echo "MALLOC_DIR = mallocng" >> config.mak > 3. Dropping the attached files into src/malloc/mallocng > 4. Symlinking or copying meta.h, malloc.c, realloc.c, free.c, > malloc_usable_size.c, and aligned_alloc.c from mallocng source dir > to src/malloc/mallocng. (You can also include dump.c if desired.) > > This produces a near-fully-integrated malloc, including support for > reclaim_gaps donation from ldso. The only functionality missing, which > I expect to flesh out before actual import, is handling of the case of > incomplete malloc replacement by interposition (__malloc_replaced!=0). > > Please report any problems encountered. For reference -- I should have mentioned in the original post -- the above is with musl commit 384c0131ccda2656dec23a0416ad3f14101151a7 and mallocng-draft commit c0d6d87596f565e652e126f54aa1a2afaecc0e52. I'll have an update to these posted soon. Rich