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 20917 invoked from network); 15 Oct 2020 20:05:22 -0000 Received: from mother.openwall.net (195.42.179.200) by inbox.vuxu.org with ESMTPUTF8; 15 Oct 2020 20:05:22 -0000 Received: (qmail 23858 invoked by uid 550); 15 Oct 2020 20:05:18 -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 23839 invoked from network); 15 Oct 2020 20:05:17 -0000 Date: Thu, 15 Oct 2020 16:05:06 -0400 From: Rich Felker To: Alexey Izbyshev Cc: musl@lists.openwall.com Message-ID: <20201015200505.GX17637@brightrain.aerifal.cx> References: <948f6fc6f3458f18152c0f8b505beec0@ispras.ru> <20201015085024.GR2947641@port70.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Subject: Re: [musl] Why is setrlimit() considered to have per-thread effect? On Thu, Oct 15, 2020 at 06:50:41PM +0300, Alexey Izbyshev wrote: > >>Tangentially, setgroups() is not called via __synccall(), though > >>it does > >>have per-thread effect. Is this intentional? > > > >that may be a bug, but it's not a posix api > >so not a conformance issue, but a linux issue: > >if other linux libcs don't do synccall then > >that's the defacto interface contract. > > > FWIW, glibc does synccall since 2011: > https://sourceware.org/git/?p=glibc.git;a=commit;h=70181fddf14 Thanks, looks like we should do the same here. Rich