From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: Andy Lutomirski <luto@amacapital.net>
Cc: mtk.manpages@gmail.com,
"Eric W. Biederman" <ebiederm@xmission.com>,
lkml <linux-kernel@vger.kernel.org>,
"linux-man@vger.kernel.org" <linux-man@vger.kernel.org>,
Linux Containers <containers@lists.linux-foundation.org>,
richard -rw- weinberger <richard.weinberger@gmail.com>,
"Serge E. Hallyn" <serge@hallyn.com>
Subject: Re: For review: user_namespace(7) man page
Date: Sat, 13 Sep 2014 19:58:32 -0700 [thread overview]
Message-ID: <54150458.9060408@gmail.com> (raw)
In-Reply-To: <CALCETrXOgCUrrzeJYJ6VoPgR5Rt0HFCrhRC0H7+3XLv1Y+sJ_A@mail.gmail.com>
On 09/11/2014 08:15 AM, Andy Lutomirski wrote:
> On Thu, Sep 11, 2014 at 7:47 AM, Michael Kerrisk (man-pages)
> <mtk.manpages@gmail.com> wrote:
>>
>> So, in the current draft of the setns(2) page, there is
>>
>> CLONE_NEWNS
>> ...
>> Since Linux 3.9, CLONE_NEWUSER also automatically implies
>> CLONE_FS.
>>
>> Does that cover your point? Or did you mean that more needs to be said?
>
> Looks good, although you could add CLONE_THREAD and the rest of the
> things implied by CLONE_THREAD if you want to be fancier.
Yes, under CLONE_NEWUSER there is also a statement that that flag
implies CLONE_THREAD, and elsewhere in the page there is the
following text:
[[
In addition, CLONE_THREAD, CLONE_SIGHAND, and CLONE_VM can be
specified in flags if the caller is single threaded (i.e., it
is not sharing its address space with another process or
thread). In this case, these flags have no effect. (Note also
that specifying CLONE_THREAD automatically implies CLONE_VM,
and specifying CLONE_VM automatically implies CLONE_SIGHAND.)
If the process is multithreaded, then the use of these flags
results in an error.
]]
Cheers,
Michael
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
next prev parent reply other threads:[~2014-09-14 2:58 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-20 23:36 For review: user_namespace(7) man page Michael Kerrisk (man-pages)
2014-08-22 21:12 ` Serge E. Hallyn
2014-09-01 16:58 ` Michael Kerrisk (man-pages)
2014-08-30 21:53 ` Eric W. Biederman
2014-09-01 17:31 ` Michael Kerrisk (man-pages)
2014-09-02 1:05 ` Eric W. Biederman
2014-09-09 14:00 ` Michael Kerrisk (man-pages)
2014-09-09 16:16 ` Eric W. Biederman
2014-09-11 14:40 ` Michael Kerrisk (man-pages)
2014-09-09 13:59 ` Michael Kerrisk (man-pages)
2014-09-09 15:49 ` Eric W. Biederman
2014-09-11 14:40 ` Michael Kerrisk (man-pages)
2014-09-09 13:59 ` Michael Kerrisk (man-pages)
2014-09-09 15:51 ` Eric W. Biederman
2014-09-11 14:40 ` Michael Kerrisk (man-pages)
2014-09-01 20:57 ` Andy Lutomirski
2014-09-09 14:00 ` Michael Kerrisk (man-pages)
2014-09-09 16:05 ` Eric W. Biederman
2014-09-09 19:26 ` Andy Lutomirski
2014-09-09 19:39 ` Andy Lutomirski
2014-09-11 14:47 ` Michael Kerrisk (man-pages)
2014-09-11 15:15 ` Andy Lutomirski
2014-09-14 2:58 ` Michael Kerrisk (man-pages) [this message]
2014-09-11 14:46 ` Michael Kerrisk (man-pages)
2014-09-11 15:14 ` Andy Lutomirski
2014-09-14 2:42 ` 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=54150458.9060408@gmail.com \
--to=mtk.manpages@gmail.com \
--cc=containers@lists.linux-foundation.org \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=richard.weinberger@gmail.com \
--cc=serge@hallyn.com \
/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).