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.4 required=5.0 tests=MAILING_LIST_MULTI, NICE_REPLY_A,RCVD_IN_DNSWL_MED,RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 18662 invoked from network); 16 Aug 2020 07:05:47 -0000 Received: from mother.openwall.net (195.42.179.200) by inbox.vuxu.org with ESMTPUTF8; 16 Aug 2020 07:05:47 -0000 Received: (qmail 16081 invoked by uid 550); 16 Aug 2020 07:05:43 -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 16063 invoked from network); 16 Aug 2020 07:05:42 -0000 X-Virus-Scanned: by amavisd-new-2.10.1 (20141025) (Debian) at wwcom.ch To: musl@lists.openwall.com, Rich Felker References: <20200814214136.GP3265@brightrain.aerifal.cx> From: Pirmin Walthert Message-ID: Date: Sun, 16 Aug 2020 09:05:28 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.11.0 MIME-Version: 1.0 In-Reply-To: <20200814214136.GP3265@brightrain.aerifal.cx> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US Subject: Re: [musl] Restrictions on child context after multithreaded fork Dear Rich, > I've seen suspicions that the switch to mallocng exposed this, but I'm > pretty sure it was: > > https://git.musl-libc.org/cgit/musl/commit/?id=e01b5939b38aea5ecbe41670643199825874b26c I needed to patch asterisk because of similar issues (you gave me some hints on this mailing list after I'd described the issue): https://issues.asterisk.org/jira/browse/ASTERISK-28776 However this happened with a combination of musl 1.2.0, which did not have the mentioned commit applied, and mallocng (LD_PRELOAD method). Asterisk with 1.2.0 and old malloc was running just fine.