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 30746 invoked from network); 16 Aug 2020 09:10:54 -0000 Received: from mother.openwall.net (195.42.179.200) by inbox.vuxu.org with ESMTPUTF8; 16 Aug 2020 09:10:54 -0000 Received: (qmail 22125 invoked by uid 550); 16 Aug 2020 09:10:50 -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 22107 invoked from network); 16 Aug 2020 09:10:49 -0000 From: Florian Weimer To: Rich Felker Cc: musl@lists.openwall.com References: <20200814214136.GP3265@brightrain.aerifal.cx> <20200816035759.GW3265@brightrain.aerifal.cx> Date: Sun, 16 Aug 2020 11:10:37 +0200 In-Reply-To: <20200816035759.GW3265@brightrain.aerifal.cx> (Rich Felker's message of "Sat, 15 Aug 2020 23:57:59 -0400") Message-ID: <87h7t3j6r6.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: > On some inspection, glibc does not actually attempt to make the child > environment unrestricted. The only things it does around fork are: I think pthread_once initializers that have partially executed are also executed from the start in the child if initialization is requested again.