From: Paul Pluzhnikov <ppluzhnikov@google.com>
To: "Robert Święcki" <robert@swiecki.net>
Cc: GLIBC Devel <libc-alpha@sourceware.org>
Subject: Re: Caching of PID/TID after fork
Date: Thu, 06 Oct 2016 16:34:00 -0000 [thread overview]
Message-ID: <CALoOobNTyKufxQOrHBNeaXxtH_28c=VCbqkpp9SBwwg+KpQFww@mail.gmail.com> (raw)
In-Reply-To: <CAP145pj+yVz_7ZF8_dNqZ2NE22A_O5QyT195Gy0TgvKq1j3skw@mail.gmail.com>
On Thu, Oct 6, 2016 at 9:13 AM, Robert Święcki <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 past, e.g.
https://sourceware.org/bugzilla/show_bug.cgi?id=19957
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
next prev parent reply other threads:[~2016-10-06 16:34 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-06 16:13 Robert Święcki
2016-10-06 16:34 ` Paul Pluzhnikov [this message]
2016-10-06 17:03 ` Robert Święcki
2016-10-06 18:32 ` Adhemerval Zanella
2016-10-06 17:26 ` Rich Felker
2016-10-06 17:42 ` Robert Święcki
2016-10-06 18:05 ` Rich Felker
2016-10-06 18:26 ` Robert Święcki
2016-10-06 21:35 ` Robert Święcki
2016-10-07 0:42 ` Zack Weinberg
2016-10-07 0:43 ` Zack Weinberg
2016-10-07 14:44 ` Robert Święcki
2016-10-07 18:20 ` Adhemerval Zanella
2016-10-07 18:30 ` Adhemerval Zanella
2016-10-07 19:38 ` Florian Weimer
2016-10-07 21:23 ` Robert Święcki
2016-10-09 10:05 ` Florian Weimer
2016-10-09 14:19 ` Robert Święcki
2016-10-10 18:03 ` Adhemerval Zanella
2016-11-04 15:14 ` Florian Weimer
2016-11-04 16:03 ` Adhemerval Zanella
2016-11-07 16:04 ` Florian Weimer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CALoOobNTyKufxQOrHBNeaXxtH_28c=VCbqkpp9SBwwg+KpQFww@mail.gmail.com' \
--to=ppluzhnikov@google.com \
--cc=libc-alpha@sourceware.org \
--cc=robert@swiecki.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).