On 09/11/2014 08:15 AM, Andy Lutomirski wrote:
> On Thu, Sep 11, 2014 at 7:47 AM, Michael Kerrisk (man-pages)
> <mtk.manpa...@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/
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
