From: Adhemerval Zanella <adhemerval.zanella@linaro.org>
To: Florian Weimer <fweimer@redhat.com>, libc-alpha@sourceware.org
Subject: Re: Caching of PID/TID after fork
Date: Fri, 04 Nov 2016 16:03:00 -0000 [thread overview]
Message-ID: <15886e77-0575-49f2-e989-dd12aba8dd97@linaro.org> (raw)
In-Reply-To: <03127072-f944-86de-da85-cd889ce5ed76@redhat.com>
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
next prev parent reply other threads:[~2016-11-04 16:03 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
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 [this message]
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=15886e77-0575-49f2-e989-dd12aba8dd97@linaro.org \
--to=adhemerval.zanella@linaro.org \
--cc=fweimer@redhat.com \
--cc=libc-alpha@sourceware.org \
/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).