This is the mail archive of the
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: Mon, 7 Nov 2016 17:04:36 +0100
- Subject: Re: Caching of PID/TID after fork
- Authentication-results: sourceware.org; auth=none
- References: <CAP145pj+yVz_7ZF8_dNqZ2NE22A_O5QyT195Gy0TgvKq1j3skw@mail.gmail.com> <email@example.com> <CAP145phqU29-vMNkS6zzWRJn4L_F9+zHQkybiirQndBcxJGp8g@mail.gmail.com> <firstname.lastname@example.org> <CAP145pjSBEgWS6dQ2u741m1z0VZYZ49ydLe-yvmjj1FuC_zqpQ@mail.gmail.com> <email@example.com> <firstname.lastname@example.org> <email@example.com>
On 11/04/2016 05:03 PM, Adhemerval Zanella wrote:
On 04/11/2016 13:14, Florian Weimer wrote:
On 10/10/2016 08:03 PM, Adhemerval Zanella wrote:
+ /* Some sanity checks for clone syscall: returned ppid should be 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.
I am not sure if you referring you to my initial RFC patch or the one
complete I sent  since you replied to the original thread.
Oh, I'll have a look at the updated patch then.