From: "Serge E. Hallyn" <serge@hallyn.com>
To: Alejandro Colomar <alx@kernel.org>
Cc: "Serge E. Hallyn" <serge@hallyn.com>,
linux-man@vger.kernel.org, Sargun Dhillon <sargun@sargun.me>,
John Watts <contact@jookia.org>
Subject: Re: [PATCH v2] clone.2: Fix outdated statement about CLONE_NEWPID
Date: Sun, 13 Aug 2023 08:53:33 -0500 [thread overview]
Message-ID: <20230813135333.GA1148436@mail.hallyn.com> (raw)
In-Reply-To: <915f236b-499d-a9c1-0d60-c8edd0eba962@kernel.org>
On Sun, Aug 13, 2023 at 03:40:36PM +0200, Alejandro Colomar wrote:
> Hi Serge,
>
> On 2023-08-13 15:35, Serge E. Hallyn wrote:
> [...]
>
> >
> > Well no, I don't think that's right. That implies that the
> > CLONE_PARENT check was a long standing one. In fact, the
> > point was that it was a regression introduced in
> >
> > 40a0d32d1 (Wed Sep 11 14:19:41 2013 -0700)
> >
> > and then fixed in 1f7f4dde5 two months later.
>
> Thanks! I'll rewrite the commit accordingly (more like Sargun's v1)
> and include this info.
Thanks :)
-serge
next prev parent reply other threads:[~2023-08-13 13:53 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 [this message]
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
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=20230813135333.GA1148436@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