From: Josh Triplett <josh-iaAMLnmF4UmaiuxdJuQwMA@public.gmane.org>
To: "Michael Kerrisk (man-pages)"
<mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-man <linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH] clone.2: Document that clone silently ignores CLONE_PID and CLONE_STOPPED
Date: Tue, 3 Mar 2015 00:13:37 -0800 [thread overview]
Message-ID: <20150303081337.GA25326@thin> (raw)
In-Reply-To: <54F55C7F.10909-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
On Tue, Mar 03, 2015 at 08:02:23AM +0100, Michael Kerrisk (man-pages) wrote:
> Hi Josh,
>
> On 03/02/2015 05:40 PM, josh-iaAMLnmF4UmaiuxdJuQwMA@public.gmane.org wrote:
> > On Mon, Mar 02, 2015 at 05:27:38PM +0100, Michael Kerrisk (man-pages) wrote:
> >> On 27 February 2015 at 17:31, <josh-iaAMLnmF4UmaiuxdJuQwMA@public.gmane.org> wrote:
> >>> On Fri, Feb 27, 2015 at 07:42:44AM +0100, Michael Kerrisk (man-pages) wrote:
> >>>> On 02/27/2015 01:41 AM, Josh Triplett wrote:
> >>>>> Normally, system calls return EINVAL for flags they don't support.
> >>>>> Explicitly document that clone does *not* produce an error for these two
> >>>>> obsolete flags.
> >>>>
> >>>> Thanks, Josh! Applied.
> >>>
> >>> Doesn't appear to be in the current git repository.
> >>
> >> Pushed now, Josh. (I needed to get another release out of the way first.)
> >
> > No problem; thanks for the update.
> >
> > Related issue: the errors section of clone.2 claims it'll return EPERM
> > for CLONE_PID by something other than PID 0 (meaning, outside the
> > kernel), but that doesn't actually happen. Should that be dropped? (I
> > can send a patch if so.)
>
> I'd take a patch to fix that. (But note, if this is kernel behavior
> that has changed over time, it would be valuable to document when
> the change occurred.)
The manpage already documents that earlier, when mentioning CLONE_PID:
CLONE_PID (obsolete)
If CLONE_PID is set, the child process is created with the same
process ID as the calling process. This is good for hacking the
system, but otherwise of not much use. Since 2.3.21 this flag
can be specified only by the system boot process (PID 0). It
disappeared in Linux 2.5.16.
- Josh Triplett
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2015-03-03 8:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-27 0:41 [PATCH] clone.2: Document that clone silently ignores CLONE_PID and CLONE_STOPPED Josh Triplett
2015-02-27 6:42 ` Michael Kerrisk (man-pages)
[not found] ` <54F011E4.1020502-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-02-27 16:31 ` josh-iaAMLnmF4UmaiuxdJuQwMA
2015-03-02 16:27 ` Michael Kerrisk (man-pages)
[not found] ` <CAKgNAkjCvzeo+tHUW+mwL+ptdCX7k=j8fmRX6OtLfFM9HVXJjQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-03-02 16:40 ` josh-iaAMLnmF4UmaiuxdJuQwMA
2015-03-03 7:02 ` Michael Kerrisk (man-pages)
[not found] ` <54F55C7F.10909-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-03-03 8:13 ` Josh Triplett [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=20150303081337.GA25326@thin \
--to=josh-iaamlnmf4umaiuxdjuqwma@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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).