This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: Caching of PID/TID after fork
- From: Florian Weimer <fweimer at redhat dot com>
- To: Adhemerval Zanella <adhemerval dot zanella at linaro dot org>, libc-alpha at sourceware dot org
- Date: Fri, 4 Nov 2016 16:14:53 +0100
- Subject: Re: Caching of PID/TID after fork
- Authentication-results: sourceware.org; auth=none
- References: <CAP145pj+yVz_7ZF8_dNqZ2NE22A_O5QyT195Gy0TgvKq1j3skw@mail.gmail.com> <87y4202blm.fsf@mid.deneb.enyo.de> <CAP145phqU29-vMNkS6zzWRJn4L_F9+zHQkybiirQndBcxJGp8g@mail.gmail.com> <87mvidj0qw.fsf@mid.deneb.enyo.de> <CAP145pjSBEgWS6dQ2u741m1z0VZYZ49ydLe-yvmjj1FuC_zqpQ@mail.gmail.com> <ecb5be63-de88-f05c-38ad-65e20f17a274@linaro.org>
On 10/10/2016 08:03 PM, Adhemerval Zanella wrote:
+ /* Some sanity checks for clone syscall: returned ppid should be currernt
Typo: “currernt”
On its own, this approach looks okay, but I am worried that it sends a
message that it's okay to clone processes without additional measures to
protect PRNGs and things like that.
Florian