Caching of PID/TID after fork

[Adhemerval Zanella]

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
> 
> 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

I am not sure if you referring you to my initial RFC patch or the one 
complete I sent [1] since you replied to the original thread.

Anyway, I see that with current fixes on some algorithm (execv not
using dynamic memory allocation and various issues with posix_spawn)
clone direct usage should be really required in very specific
scanerios (mostly on new containers projects and such alike).  And 
I would expect that these very projects to know the constraints and 
limitations of using the syscall directly.

[1] https://sourceware.org/ml/libc-alpha/2016-10/msg00233.html