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 7014 invoked from network); 14 Aug 2020 22:02:22 -0000 Received: from mother.openwall.net (195.42.179.200) by inbox.vuxu.org with ESMTPUTF8; 14 Aug 2020 22:02:22 -0000 Received: (qmail 19463 invoked by uid 550); 14 Aug 2020 22:02:17 -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 18421 invoked from network); 14 Aug 2020 22:02:17 -0000 From: Florian Weimer To: Rich Felker Cc: musl@lists.openwall.com References: <20200814214136.GP3265@brightrain.aerifal.cx> Date: Sat, 15 Aug 2020 00:02:01 +0200 In-Reply-To: <20200814214136.GP3265@brightrain.aerifal.cx> (Rich Felker's message of "Fri, 14 Aug 2020 17:41:38 -0400") Message-ID: <871rk8opie.fsf@mid.deneb.enyo.de> MIME-Version: 1.0 Content-Type: text/plain Subject: Re: [musl] Restrictions on child context after multithreaded fork * Rich Felker: > In case we do want to follow a direction of trying to provide some > degree of relaxation of restrictions on the child (taking the liberty > of POSIX-future drop of fork's AS-safety requirement), I did a quick > survey of libc-internal locks, and found: pthread_once is another source of problems, although there seem to be few users in musl.