musl - Re: Why is setrlimit() considered to have per-thread effect?

Follow @Openwall on Twitter for new release announcements and other news

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20201015200505.GX17637@brightrain.aerifal.cx>
Date: Thu, 15 Oct 2020 16:05:06 -0400
From: Rich Felker <dalias@...c.org>
To: Alexey Izbyshev <izbyshev@...ras.ru>
Cc: musl@...ts.openwall.com
Subject: Re: 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

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.