From: "Michael Kerrisk" <mtk.manpages@googlemail.com>
To: "Serge E. Hallyn" <serge@hallyn.com>
Cc: Pavel Emelyanov <xemul@openvz.org>,
Kir Kolyshkin <kir@openvz.org>,
linux-man@vger.kernel.org, lkml <linux-kernel@vger.kernel.org>,
Sukadev Bhattiprolu <sukadev@us.ibm.com>,
Nadia Derbey <Nadia.Derbey@bull.net>
Subject: Re: Documentation for CLONE_NEWPID
Date: Tue, 25 Nov 2008 10:09:27 -0500 [thread overview]
Message-ID: <cfd18e0f0811250709x4e2cc5cdhafb9ccf494890442@mail.gmail.com> (raw)
In-Reply-To: <20081123222023.GB12687@hallyn.com>
Hi Serge,
[...]
>> +PID namespaces form a hierarchy.
>> +When a PID new namespace is created,
>> +the PIDs of the processes in that namespace are visible
>
> The processes in that namespace are visible, but by different
> pids. So saying that the pids are visible in the parent
> pidns isn't quite right.
Yes, good point. I made that last line:
"... the processes in that namespace are visible..."
>> +in the PID namespace of the process that created the new namespace;
>> +analogously, if the parent PID namespace is itself
>> +the child of another PID namespace,
>> +then PIDs of the child and parent PID namespaces will both be
>
> Again, the processes, not pids, are visible.
Yep. Fixed.
[...]
>> +After creating the new namespace,
>> +it is useful for the child to change its root directory
>> +and mount a new procfs instance at
>> +.I /proc
>> +so that tools such as
>> +.BR ps (1)
>> +work correctly.
>
> Probably not worth mentioning here, but if it has done
> CLONE_NEWNS then it doesn't need to change its root, it
> can just mount a new proc instance over /proc.
Actually, I think it is worth mentioning. When I wrote the text, I
suspected that the point you make here was true, but I wasn't 100%
sure. Therefore, I think it worth adding a sentence like your comment
here, and I've done so.
[...]
> I assume you've considered the pros and cons of mentioning
> signal semantics with respect to init tasks of child pid namespaces,
> and decided it's not worth mentioning yet as the semantics are not
> yet finalized?
>
> The goal is to treat the process as a system-wide init with respect
> to signals coming from its own namespace, and treat it as an ordinary
> task for signals coming from its ancestor namespaces. But as you've
> probably read, the implementation may result in some unfortunate
> side-effects regarding blocked signals etc.
No I haven't considered this at all. Could you provide some pointers
to relevant discussions on this?
Cheers,
Michael
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
git://git.kernel.org/pub/scm/docs/man-pages/man-pages.git
man-pages online: http://www.kernel.org/doc/man-pages/online_pages.html
Found a bug? http://www.kernel.org/doc/man-pages/reporting_bugs.html
next prev parent reply other threads:[~2008-11-25 15:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-19 2:59 Documentation for CLONE_NEWPID Michael Kerrisk
[not found] ` <4923810B.7010201-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2008-11-23 22:20 ` Serge E. Hallyn
2008-11-25 15:09 ` Michael Kerrisk [this message]
[not found] ` <cfd18e0f0811250709x4e2cc5cdhafb9ccf494890442-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-11-26 17:08 ` Serge E. Hallyn
2008-11-24 12:46 ` Pavel Emelyanov
[not found] ` <492AA241.6050004-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>
2008-11-25 15:46 ` Michael Kerrisk
[not found] ` <cfd18e0f0811250746i711205dej6b98f2fba6cecc42-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-11-25 15:54 ` Pavel Emelyanov
2008-11-25 16:27 ` Michael Kerrisk
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=cfd18e0f0811250709x4e2cc5cdhafb9ccf494890442@mail.gmail.com \
--to=mtk.manpages@googlemail.com \
--cc=Nadia.Derbey@bull.net \
--cc=kir@openvz.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
--cc=serge@hallyn.com \
--cc=sukadev@us.ibm.com \
--cc=xemul@openvz.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