Re: [PATCH 1/2] setns.2: Initial man page [RESEND]
From: Michael Kerrisk
Date: Mon Oct 03 2011 - 09:36:12 EST
On Thu, Sep 29, 2011 at 1:28 AM, Eric W. Biederman
> Michael Kerrisk <mtk.manpages@xxxxxxxxx> writes:
>> Hi Eric,
>> I'm still wanting your input on the edited setns.2 draft below. Please
>> don't make me chase you round Prague ;-).
> That could be interesting... As I don't have plans to head out that way
> this year. I got side tracked with some unexpected computer troubles
> that showed up right after I got home.
Ahh -- that's a shame not to see you there!
> So overall it looks good. I found two nits to pick (see below).
> The significant nit is how do we say unshare and setns refer
> to just a linux task and not the entire process.
> When you are writing multi-threaded apps it actually matters.
> In particular I keep expecting someone will need a call like:
> int socketat(int namespace, int domain, int type, int protocol)
> int netns, ret, fd;
> netns = open("/proc/self/ns/net", O_RDONLY);
> if (netns < 0)
> return -1;
> ret = setns( namespace, CLONE_NETNS);
> if (ret < 0)
> return -1;
> fd = socket( domain, type, protocol);
> setns(netns, CLONE_NETNS);
> return fd;
> Which with a little bit care adding blocking of signals etc
> that call can actually be made thread safe.
> However if setns affected all threads of a multi-threaded process
> socketat would require a system call to be written to do the
> same job.
Okay. But please, when you add it, don't call it "socketat()". That
name makes it look as though it is similar to "openat()" and all of
the other "*at" calls, when really it is not. Perhaps "socketns()"?
> Multi-threaded processes that simultaneously deal with multiple
> namespaces are likely to be rare but I expect there to be a few
> that actually care.
>> From: Michael Kerrisk <mtk.manpages@xxxxxxxxx>
>> Date: Thu, Sep 15, 2011 at 6:13 AM
>> Subject: Re: [PATCH 1/2] setns.2: Initial man page
>> To: "Eric W. Biederman" <ebiederm@xxxxxxxxxxxx>
>> Cc: linux-man@xxxxxxxxxxxxxxx, "Serge E. Hallyn" <serge.hallyn@xxxxxxxxxxxxx>
>> Hello Eric,
>> See below.
>> On Mon, May 30, 2011 at 5:16 AM, Eric W. Biederman
>> <ebiederm@xxxxxxxxxxxx> wrote:
>>> Signed-off-by: Eric W. Biederman <ebiederm@xxxxxxxxxxxx>
>>> man2/setns.2 | 88 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>> 1 files changed, 88 insertions(+), 0 deletions(-)
>>> create mode 100644 man2/setns.2
>>> diff --git a/man2/setns.2 b/man2/setns.2
>>> new file mode 100644
>>> index 0000000..8b48e14
>>> --- /dev/null
>>> +++ b/man2/setns.2
>>> @@ -0,0 +1,88 @@
>>> +.\" Copyright (C) 2011, Eric Biederman <ebiederm@xxxxxxxxxxxx>
>>> +.\" Licensed under the GPLv2
>> As I understand it, this refers to interactions between the mount
>> namespace and file system namespace. However, as noted in the man
>> page, setns() does not support CLONE_NEWNS. Furthermore, I can see no
>> path in the setns() that generates EINVAL and involves CLONE_NEWNS.
>> So,I removed that text. Please let me know if that's wrong.
> Removing that text is fine for now. I expect I will have to readd it
> after I get my next round of patches in but no need to Document what
> does not yet exist in mainline.
> Reading the
>> .\" Copyright (C) 2011, Eric Biederman <ebiederm@xxxxxxxxxxxx>
>> .\" Licensed under the GPLv2
>> .TH SETNS 2 2011-09-15 "Linux" "Linux Programmer's Manual"
>> .SH NAME
>> setns \- reassociate process with a namespace
>> .SH SYNOPSIS
>> .BR "#define _GNU_SOURCE" " /* See feature_test_macros(7) */"
>> .B #include <sched.h>
>> .BI "int setns(int " fd ", int " nstype );
>> .SH DESCRIPTION
>> Given a file descriptor referring to a namespace,
>> reassociate the calling process with that namespace.
>> .I fd
>> argument is a file descriptor referring to one of the namespace entries in a
>> .I /proc/[pid]/ns/
>> directory; see
>> .BR proc (5)
>> for further information on
>> .IR /proc/[pid]/ns/ .
>> The calling process will be reassociated with the corresponding namespace,
>> subject to any constraints imposed by the
>> .I nstype
> There is an weird twist I think it makes sense to document. The unit of
> reassociation is a linux task. What is normally seen as a thread.
> Which is important to consider if you happen to be using this in a
> multi-threaded program. But I'm not certain how best to say that.
> Perhaps: perhaps just say linux task instead of process?
I'll write "thread", which is the usual terminology in this context
(Section 2). I've made that change at multiple places in the page (see
>> .SH ERRORS
>> .B EBADF
>> .I fd
>> is not a valid file descriptor.
>> .B EINVAL
>> .I fd
>> refers to a namespace whose type does not match that specified in
>> .IR nstype .
> Just because we have been going back on forth on this bit I am inclined
> to say:
> EINVAL fd refers to a namespace whose type does not match that
> specified in nstype, or there is problem with reassociating the
> the thread with the specified namespace.
Revised page below, which you can make a final check on, if you like.
The page will go out with the next man-pages release (3.35).
.\" Copyright (C) 2011, Eric Biederman <ebiederm@xxxxxxxxxxxx>
.\" Licensed under the GPLv2
.TH SETNS 2 2011-09-15 "Linux" "Linux Programmer's Manual"
setns \- reassociate thread with a namespace
.BR "#define _GNU_SOURCE" " /* See feature_test_macros(7) */"
.B #include <sched.h>
.BI "int setns(int " fd ", int " nstype );
Given a file descriptor referring to a namespace,
reassociate the calling thread with that namespace.
argument is a file descriptor referring to one of the namespace entries in a
.BR proc (5)
for further information on
.IR /proc/[pid]/ns/ .
The calling thread will be reassociated with the corresponding namespace,
subject to any constraints imposed by the
argument specifies which type of namespace
the calling thread may be reassociated with.
This argument can have one of the following values:
Allow any type of namespace to be joined.
must refer to an IPC namespace.
must refer to a network namespace.
must refer to a UTS namespace.
as 0 suffices if the caller knows (or does not care)
what type of namespace is referred to by
.IR fd .
Specifying a nonzero value for
is useful if the caller does not know what type of namespace is referred to by
and wants to ensure that the namespace is of a particular type.
(The caller might not know the type of the namespace referred to by
if the file descriptor was opened by another process and, for example,
passed to the caller via a UNIX domain socket.)
.SH RETURN VALUE
.IR setns ()
On failure, \-1 is returned and
is set to indicate the error.
is not a valid file descriptor.
refers to a namespace whose type does not match that specified in
.IR nstype ,
or there is problem with reassociating the
the thread with the specified namespace.
Cannot allocate sufficient memory to change the specified namespace.
The calling thread did not have the required privilege
.RB ( CAP_SYS_ADMIN )
for this operation.
.BR setns ()
system call first appeared in Linux in kernel 3.0
.SH CONFORMING TO
.BR setns ()
system call is Linux-specific.
Not all of the attributes that can be shared when
a new thread is created using
.BR clone (2)
can be changed using
.BR setns ().
The PID namespace and the mount namespace are not currently supported.
(See the descriptions of
.BR clone (2).)
.SH SEE ALSO
.BR clone (2),
.BR fork (2),
.BR vfork (2),
.BR proc (5),
.BR unix (7)
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Author of "The Linux Programming Interface"; http://man7.org/tlpi/
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/