From: Rich Felker <dalias@libc.org>
To: "Robert Święcki" <robert@swiecki.net>
Cc: libc-alpha@sourceware.org
Subject: Re: Caching of PID/TID after fork
Date: Thu, 06 Oct 2016 17:26:00 -0000 [thread overview]
Message-ID: <20161006172631.GO19318@brightrain.aerifal.cx> (raw)
In-Reply-To: <CAP145pj+yVz_7ZF8_dNqZ2NE22A_O5QyT195Gy0TgvKq1j3skw@mail.gmail.com>
On Thu, Oct 06, 2016 at 06:13:41PM +0200, Robert ÅwiÄcki wrote:
> Hi,
>
> This has probably been debated a lot of times in the past, but...
>
> A lot of tool these days create Linux namespaces, using clone(). Using
> glibc's clone() is not the best option, because e.g. it requires stack
> pointer, (and fails with some error if it's NULL), while Linux kernel
> will happily reuse the current SP (no need to write additional code to
> deal with that). So, glibc's clone() adds imposed additional
> restrictions wrt kernel.
>
> And, after that getpid() will return old PID/TID.
>
> It seems that currently Linux supports getpid() via vsyscall (fast) on
> x86/64. Would you consider changing getpid() to be a wrapper to
> syscall(__NR_getpid)?
>
> One could say that if somebody uses syscall(__NR_clone) she/he should
> be using syscall(__NR_getpid) as well, but in case of software
> libraries, which might be preparing namespaces, the caller of the lib
> might know nothing about the exact method used to create a new
> process.
>
> Thefore I'd like to ask for one of the following solutions:
>
> 1. Don't cache PID/TID
>
> 2. Provide some kind of symbol, which would force for TID/PID to be
> reloaded in glibc.
There's an easy solution that works with existing versions of glibc
(and other libcs) with no new symbol or new symbol version dependency:
call the libc clone() function with a tiny dummy stack and a function
which does nothing but longjmp out to the caller.
Rich
next prev parent reply other threads:[~2016-10-06 17:26 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 [this message]
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=20161006172631.GO19318@brightrain.aerifal.cx \
--to=dalias@libc.org \
--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).