linux-man.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org>
To: Michael Kerrisk <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: [PATCH] setns/pid_namespaces: mention the pid ns descendant limitation more
Date: Fri,  2 Jan 2015 13:04:42 -0500	[thread overview]
Message-ID: <1420221882-12614-1-git-send-email-vapier@gentoo.org> (raw)

The setns(2) man page already mentions that CLONE_NEWPID may only be
used with descendant namespaces, but this nuance could be listed in
a few more places so it is not missed.

Signed-off-by: Mike Frysinger <vapier-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org>
---
 man2/setns.2          |  7 ++++++-
 man7/pid_namespaces.7 | 10 ++++++++++
 2 files changed, 16 insertions(+), 1 deletion(-)

diff --git a/man2/setns.2 b/man2/setns.2
index 926842b..3e6c4a5 100644
--- a/man2/setns.2
+++ b/man2/setns.2
@@ -55,7 +55,7 @@ must refer to a mount namespace.
 .TP
 .BR CLONE_NEWPID " (since Linux 3.8)"
 .I fd
-must refer to a PID namespace.
+must refer to a descendant PID namespace.
 .TP
 .BR CLONE_NEWUSER " (since Linux 3.8)"
 .I fd
@@ -157,6 +157,11 @@ refers to a namespace whose type does not match that specified in
 There is problem with reassociating
 the thread with the specified namespace.
 .TP
+.\" See kernel/pid_namespace.c::pidns_install() [kernel 3.18 sources]
+.B EINVAL
+The caller tried to join an ancestor (parent, grandparent, etc...)
+pid namespace.
+.TP
 .B EINVAL
 The caller attempted to join the user namespace
 in which it is already a member.
diff --git a/man7/pid_namespaces.7 b/man7/pid_namespaces.7
index 8582da3..89c606b 100644
--- a/man7/pid_namespaces.7
+++ b/man7/pid_namespaces.7
@@ -188,6 +188,16 @@ PID namespace from the caller of
 Calls to
 .BR getppid (2)
 for such processes return 0.
+
+While processes may freely descend into children PID namespaces
+(e.g. using
+.BR setns (2)
+with
+.BR CLONE_NEWPID ),
+they may not move in the other direction.
+That is to say, processes may not enter any ancestor namespaces
+(parent, grandparent, etc.).
+Changing PID namespaces is a one way operation.
 .\"
 .\" ============================================================
 .\"
-- 
2.2.1

--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

             reply	other threads:[~2015-01-02 18:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-02 18:04 Mike Frysinger [this message]
     [not found] ` <1420221882-12614-1-git-send-email-vapier-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org>
2015-01-06 14:20   ` [PATCH] setns/pid_namespaces: mention the pid ns descendant limitation more Michael Kerrisk (man-pages)

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=1420221882-12614-1-git-send-email-vapier@gentoo.org \
    --to=vapier-abrp7r+bbdudnm+yrofe0a@public.gmane.org \
    --cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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 NNTP newsgroup(s).