From: "Serge E. Hallyn" <serge@hallyn.com>
To: Alejandro Colomar <alx@kernel.org>
Cc: linux-man@vger.kernel.org, Sargun Dhillon <sargun@sargun.me>,
Serge Hallyn <serge@hallyn.com>, John Watts <contact@jookia.org>
Subject: Re: [PATCH v3] clone.2: Fix erroneous statement about CLONE_NEWPID|CLONE_PARENT
Date: Sun, 13 Aug 2023 09:36:10 -0500 [thread overview]
Message-ID: <20230813143610.GA1148742@mail.hallyn.com> (raw)
In-Reply-To: <20230813135525.37196-1-alx@kernel.org>
On Sun, Aug 13, 2023 at 03:55:25PM +0200, Alejandro Colomar wrote:
> From: Sargun Dhillon <sargun@sargun.me>
>
> CLONE_NEWPID|CLONE_PARENT was only prohibited during a short period.
> That prohibition was introduced in Linux 3.12, in commit 40a0d32d1eaf
> ("fork: unify and tighten up CLONE_NEWUSER/CLONE_NEWPID checks"), but
> was a regression, and was fixed in Linux 3.13, in commit 1f7f4dde5c94
> ("fork: Allow CLONE_PARENT after setns(CLONE_NEWPID)").
>
> In this test program, one can see that it works:
>
> #include <err.h>
> #include <linux/sched.h>
> #include <sched.h>
> #include <stdio.h>
> #include <stdlib.h>
> #include <sys/syscall.h>
> #include <unistd.h>
>
> static pid_t sys_clone3(struct clone_args *args);
>
> int
> main(void)
> {
> int ret;
> struct clone_args args = {
> .flags = CLONE_PARENT | CLONE_NEWPID,
> };
>
> printf("main program: pid: %d, and ppid: %d\n", getpid(), getppid());
>
> ret = sys_clone3(&args);
> switch (ret) {
> case -1:
> err(EXIT_FAILURE, "clone3");
> case 0:
> printf("child: pid: %d, and ppid: %d\n", getpid(), getppid());
> exit(EXIT_SUCCESS);
> default:
> exit(EXIT_SUCCESS);
> }
> }
>
> static pid_t
> sys_clone3(struct clone_args *args)
> {
> fflush(stdout);
> fflush(stderr);
> return syscall(SYS_clone3, args, sizeof(*args));
> }
>
> This test program (successfully) outputs:
>
> # ./a.out
> main program: pid: 34663, and ppid: 34662
> child: pid: 1, and ppid: 0
>
> Cowritten-by: Sargun Dhillon <sargun@sargun.me>
> Cc: Serge Hallyn <serge@hallyn.com>
Reviewed-by: Serge Hallyn <serge@hallyn.com>
> Cc: John Watts <contact@jookia.org>
> Signed-off-by: Alejandro Colomar <alx@kernel.org>
> ---
> man2/clone.2 | 4 +---
> 1 file changed, 1 insertion(+), 3 deletions(-)
>
> diff --git a/man2/clone.2 b/man2/clone.2
> index b91b71831..7d2dc2339 100644
> --- a/man2/clone.2
> +++ b/man2/clone.2
> @@ -736,9 +736,7 @@ .SS The flags mask
> can employ
> .BR CLONE_NEWPID .
> This flag can't be specified in conjunction with
> -.B CLONE_THREAD
> -or
> -.BR CLONE_PARENT .
> +.BR CLONE_THREAD .
> .TP
> .B CLONE_NEWUSER
> (This flag first became meaningful for
> --
> 2.40.1
next prev parent reply other threads:[~2023-08-13 14:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-10 2:26 [PATCH] clone.2: Fix the erroneous statement about CLONE_NEWPID Sargun Dhillon
2023-08-12 17:48 ` Alejandro Colomar
2023-08-12 17:51 ` Alejandro Colomar
2023-08-12 19:05 ` John Watts
2023-08-13 0:57 ` Sargun Dhillon
2023-08-13 13:17 ` [PATCH v2] clone.2: Fix outdated " Alejandro Colomar
2023-08-13 13:35 ` Serge E. Hallyn
2023-08-13 13:40 ` Alejandro Colomar
2023-08-13 13:53 ` Serge E. Hallyn
2023-08-13 13:55 ` [PATCH v3] clone.2: Fix erroneous statement about CLONE_NEWPID|CLONE_PARENT Alejandro Colomar
2023-08-13 14:03 ` Alejandro Colomar
2023-08-13 14:36 ` Serge E. Hallyn [this message]
2023-08-13 14:37 ` Alejandro Colomar
2023-08-13 14:40 ` Alejandro Colomar
2023-08-13 14:14 ` [PATCH v4] " Alejandro Colomar
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=20230813143610.GA1148742@mail.hallyn.com \
--to=serge@hallyn.com \
--cc=alx@kernel.org \
--cc=contact@jookia.org \
--cc=linux-man@vger.kernel.org \
--cc=sargun@sargun.me \
/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