From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <libc-alpha-return-73777-listarch-libc-alpha=sources.redhat.com@sourceware.org>
Received: (qmail 60800 invoked by alias); 6 Oct 2016 16:34:22 -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 60790 invoked by uid 89); 6 Oct 2016 16:34:22 -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_DNSWL_NONE,RCVD_IN_SORBS_SPAM,RP_MATCHES_RCVD,SPF_PASS autolearn=ham version=3.3.2 spammy=
X-HELO: mail-ua0-f174.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=tX4GG3ZINWnqiBmELuRz+Ob/5361NqbZbqkak8p8R5c=;
        b=BZUg3M9JmJdITdiwUg/43EGyKOnFA6pMJnIaq95bzcqyBt3lVtDA4wM8aPud8Ebxpk
         RpWSNg8NYH3d0Ge4wpRKBADAh0J+N3mhGviA+qNJAMkcIl5A60Q/ZW4grJwyZhl1PG3y
         sDLv8jiwwj8M91mYd2Ap7r8p470yMcy9zx+znsqI0WIbKX5SFMfIC/hEaCo+UXVfYsPV
         ld2bGg5H8v+V8ysPciczAGgRokyKUMeXJtYFwBTJ1KJE0pAqWfDDoNrfFFIa4RlxQNLC
         CSTQOUzirRi/DZkCI3NLFv1Rcvhs9PVa/dvt68BtlktgrAB5th0fDu1sbW/U8wKb7eRC
         +haA==
X-Gm-Message-State: AA6/9RnMKpyD8HXPpZzl9CGmdnoDe7cjBPF9/4aR9eTAp6/XE8/3m7XxRYp3y7suoSA8hls+H7631+SBSXR9/h2q
X-Received: by 10.176.0.176 with SMTP id 45mr11539809uaj.90.1475771650294;
 Thu, 06 Oct 2016 09:34:10 -0700 (PDT)
MIME-Version: 1.0
In-Reply-To: <CAP145pj+yVz_7ZF8_dNqZ2NE22A_O5QyT195Gy0TgvKq1j3skw@mail.gmail.com>
References: <CAP145pj+yVz_7ZF8_dNqZ2NE22A_O5QyT195Gy0TgvKq1j3skw@mail.gmail.com>
From: Paul Pluzhnikov <ppluzhnikov@google.com>
Date: Thu, 06 Oct 2016 16:34:00 -0000
Message-ID: <CALoOobNTyKufxQOrHBNeaXxtH_28c=VCbqkpp9SBwwg+KpQFww@mail.gmail.com>
Subject: Re: Caching of PID/TID after fork
To: =?UTF-8?B?Um9iZXJ0IMWad2nEmWNraQ==?= <robert@swiecki.net>
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/msg00137.txt.bz2

On Thu, Oct 6, 2016 at 9:13 AM, Robert =C5=9Awi=C4=99cki <robert@swiecki.ne=
t> 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 past,=
 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

--=20
Paul Pluzhnikov