linux-man.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: Adrian Reber <areber@redhat.com>,
	Christian Brauner <christian.brauner@ubuntu.com>
Cc: mtk.manpages@gmail.com, linux-man@vger.kernel.org
Subject: Re: [PATCH v2] clone.2: added clone3() set_tid information
Date: Sat, 14 Dec 2019 02:55:06 +0100	[thread overview]
Message-ID: <1dee03d2-e3f2-2f3d-f5a9-a657ce9ba85d@gmail.com> (raw)
In-Reply-To: <20191204070012.GE34164@dcbz.redhat.com>

Hi Adrian,

On 12/4/19 8:00 AM, Adrian Reber wrote:
> On Mon, Dec 02, 2019 at 11:14:55PM +0100, Christian Brauner wrote:
>> On Mon, Dec 02, 2019 at 03:27:40PM +0100, Adrian Reber wrote:
>>> Signed-off-by: Adrian Reber <areber@redhat.com>
>>
>> I'm generally fine with all of this, so:
>>
>> Acked-by: Christian Brauner <christian.brauner@ubuntu.com>
>>
>> but should this maybe also mention that a pid namespace either already
>> needs to have a pid 1 or if it does not the chosen pid has to be set to
>> 1. In short:
>> "Callers may only choose a pid > 1 in a given pid namespace if an init
>> process (i.e. a process with pid 1) already exists. Otherwise the pid
>> entry for this pid namespace must be 1."
>> or something like this. 
> 
> I like that. I will add this to v3.

Do you have that v3?

Thanks,

Michael


-- 
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/

      reply	other threads:[~2019-12-14  1:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-02 14:27 [PATCH v2] clone.2: added clone3() set_tid information Adrian Reber
2019-12-02 22:14 ` Christian Brauner
2019-12-04  7:00   ` Adrian Reber
2019-12-14  1:55     ` Michael Kerrisk (man-pages) [this message]

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=1dee03d2-e3f2-2f3d-f5a9-a657ce9ba85d@gmail.com \
    --to=mtk.manpages@gmail.com \
    --cc=areber@redhat.com \
    --cc=christian.brauner@ubuntu.com \
    --cc=linux-man@vger.kernel.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).