From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <libc-alpha-return-73781-listarch-libc-alpha=sources.redhat.com@sourceware.org>
Received: (qmail 34914 invoked by alias); 6 Oct 2016 17:03:30 -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 34803 invoked by uid 89); 6 Oct 2016 17:03:29 -0000
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.2 spammy=kernel's
X-HELO: mail-qk0-f181.google.com
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20130820;
        h=x-gm-message-state:mime-version:in-reply-to:references:from:date
         :message-id:subject:to:cc:content-transfer-encoding;
        bh=aWHiRJM63R+xSMy8wR+I0eTfEZipok4+MdjIqFkiUlo=;
        b=KmUXlGY/ezo2LmyJTBkcM6Mjt2fI4wSJaHC4w2OaBECJQ890yXz53hjJjph/xgDHSI
         UpDAD7DEEA01sMUCvG4kOxYudWVGgNuR5kU123sLqt8t6vCV7whoHrzeIT6R4Xb7K1Ej
         lgswzCux7BUSEzgZDePPRtAPXGx+1yGXtd9HDCu633EGYaei46I2+geSQxkeUCoqgcHM
         /tv+Wkvu7X1SdVy+SenZ0hI9GbWkHrFSx0Awerle/LmCR+jOLIipt3E7J46fXBaTYMVb
         VOg5gz/O4BNw6mIBAYC9pMWzluCvq7rHT6tCUmkP8ZUYSmViZ4vS2jKKReXUZJmFHYrE
         rvJg==
X-Gm-Message-State: AA6/9RkdrM3QDWZB0ocuF4REzgVZFkWJRgSN2T29DpOQQjnJvxPk7KV64BmFEoNaUim30wBq3DTaPERfnVaVdA==
X-Received: by 10.233.223.132 with SMTP id t126mr16400264qkf.107.1475773397888;
 Thu, 06 Oct 2016 10:03:17 -0700 (PDT)
MIME-Version: 1.0
In-Reply-To: <CALoOobNTyKufxQOrHBNeaXxtH_28c=VCbqkpp9SBwwg+KpQFww@mail.gmail.com>
References: <CAP145pj+yVz_7ZF8_dNqZ2NE22A_O5QyT195Gy0TgvKq1j3skw@mail.gmail.com>
 <CALoOobNTyKufxQOrHBNeaXxtH_28c=VCbqkpp9SBwwg+KpQFww@mail.gmail.com>
From: =?UTF-8?B?Um9iZXJ0IMWad2nEmWNraQ==?= <robert@swiecki.net>
Date: Thu, 06 Oct 2016 17:03:00 -0000
Message-ID: <CAP145pivK3gmtZ0oTz0E6RcC52e++ARPj7wjACqFo7xHezmDew@mail.gmail.com>
Subject: Re: Caching of PID/TID after fork
To: Paul Pluzhnikov <ppluzhnikov@google.com>
Cc: GLIBC Devel <libc-alpha@sourceware.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-SW-Source: 2016-10/txt/msg00141.txt.bz2

3. Provide clone() wrapper, which doesn't impose additional
restrictions over kernel's __NR_clone and which updates the TID/PID
cache.

2016-10-06 18:33 GMT+02:00 Paul Pluzhnikov <ppluzhnikov@google.com>:
> On Thu, Oct 6, 2016 at 9:13 AM, Robert =C5=9Awi=C4=99cki <robert@swiecki.=
net> wrote:
>
>> This has probably been debated a lot of times in the past, but...
>
> We should probably mention that caching of PID has caused bugs in the pas=
t, e.g.
> https://sourceware.org/bugzilla/show_bug.cgi?id=3D19957
> https://sourceware.org/ml/libc-alpha/2006-07/msg00123.html
>
> There is also
> http://www.eglibc.org/archives/issues/msg00061.html
> http://yarchive.net/comp/linux/getpid_caching.html
>
> --
> Paul Pluzhnikov



--=20
Robert =C5=9Awi=C4=99cki