[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5d941e9e-aba9-8929-66e9-93ae19e11757@gmail.com>
Date: Wed, 25 Sep 2019 16:02:01 +0200
From: "Michael Kerrisk (man-pages)" <mtk.manpages@...il.com>
To: Florian Weimer <fw@...eb.enyo.de>
Cc: mtk.manpages@...il.com,
Christian Brauner <christian.brauner@...ntu.com>,
Oleg Nesterov <oleg@...hat.com>, Jann Horn <jannh@...gle.com>,
"Eric W. Biederman" <ebiederm@...ssion.com>,
Daniel Colascione <dancol@...gle.com>,
Joel Fernandes <joel@...lfernandes.org>,
linux-man <linux-man@...r.kernel.org>,
Linux API <linux-api@...r.kernel.org>,
lkml <linux-kernel@...r.kernel.org>
Subject: Re: For review: pidfd_send_signal(2) manual page
On 9/25/19 3:51 PM, Florian Weimer wrote:
> * Michael Kerrisk:
>
>> If these conditions don't hold true, then the child process should
>> instead be created using clone(2) with the CLONE_PID flag.
>
> I think this should be CLONE_PIDFD.
Thanks Florian. Fixed.
Cheers,
Michael
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
Powered by blists - more mailing lists