From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <libc-alpha-return-73800-listarch-libc-alpha=sources.redhat.com@sourceware.org>
Received: (qmail 90675 invoked by alias); 7 Oct 2016 00:42:26 -0000
Mailing-List: contact libc-alpha-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <libc-alpha.sourceware.org>
List-Subscribe: <mailto:libc-alpha-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/libc-alpha/>
List-Post: <mailto:libc-alpha@sourceware.org>
List-Help: <mailto:libc-alpha-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: libc-alpha-owner@sourceware.org
Received: (qmail 90647 invoked by uid 89); 7 Oct 2016 00:42:23 -0000
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-4.0 required=5.0 tests=AWL,BAYES_00,RCVD_IN_SORBS_SPAM,RP_MATCHES_RCVD,SPF_PASS autolearn=ham version=3.3.2 spammy=Hx-languages-length:749
X-HELO: mailbackend.panix.com
X-Gm-Message-State: AA6/9RnC1Ak24asKCUPpPIIP4uFI22oyOfcN+Z8rg3S0wxjoicJlIEq3ZcZymzNmId1nKw7bDimeCZ2vwNQ9LQ==
X-Received: by 10.28.88.70 with SMTP id m67mr15559903wmb.14.1475800930779;
 Thu, 06 Oct 2016 17:42:10 -0700 (PDT)
MIME-Version: 1.0
In-Reply-To: <CAP145pgU=Ph1UHntkZoEFwneEGCVzzb8YhyzjJBt69wxPemRkg@mail.gmail.com>
References: <CAP145pj+yVz_7ZF8_dNqZ2NE22A_O5QyT195Gy0TgvKq1j3skw@mail.gmail.com>
 <20161006172631.GO19318@brightrain.aerifal.cx> <CAP145pjLiwhx4P3XJQCBrpg=OBmaHWyHHOkvT82eSJ4s8aFLZQ@mail.gmail.com>
 <20161006180514.GP19318@brightrain.aerifal.cx> <CAP145phG3DL2nFmA32Lu2J_aQEahKT1CoZrNJaGDn76Mov32Ww@mail.gmail.com>
 <CAP145pgU=Ph1UHntkZoEFwneEGCVzzb8YhyzjJBt69wxPemRkg@mail.gmail.com>
From: Zack Weinberg <zackw@panix.com>
Date: Fri, 07 Oct 2016 00:42:00 -0000
X-Gmail-Original-Message-ID: <CAKCAbMhZ4ddn3RrqkKg2fr_x_pK6X7DwmPVfb3ZLvcZJqGVJJA@mail.gmail.com>
Message-ID: <CAKCAbMhZ4ddn3RrqkKg2fr_x_pK6X7DwmPVfb3ZLvcZJqGVJJA@mail.gmail.com>
Subject: Re: Caching of PID/TID after fork
To: =?UTF-8?B?Um9iZXJ0IMWad2nEmWNraQ==?= <robert@swiecki.net>
Cc: Adhemerval Zanella <adhemerval.zanella@linaro.org>, GLIBC Devel <libc-alpha@sourceware.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-SW-Source: 2016-10/txt/msg00160.txt.bz2

On Thu, Oct 6, 2016 at 5:35 PM, Robert =C5=9Awi=C4=99cki <robert@swiecki.ne=
t> wrote:
>
> Maybe providing something like fork_with_flags(int flags) would work
> here? Seems that most (all?) the projects that I've seen, which use
> clone() directly and had problems with caching of TID/PID, basically
> need fork with some flags (mainly of the CLONE_NEW* type). Such
> function would deal with tid/gid/locks/pthread_atfork as fork does,
> but would also OR the provided flags with the canonical ones?

I've thought for quite some time that there should be a second
clone-wrapper in glibc that doesn't ask for a new stack.  It might be
better to call it something with "clone" in the name, but I don't care
terribly much.

zw