Skip to contentSkip to conversation

clone.2: Document that clone silently ignores CLONE_PID and CLONE_STOPPED

PATCH In review Josh Triplett 2 participants 7 messages Feb 27, 2015 – Mar 3, 2015 3 messages not in the archive Man-pages: manual pages for Linux -- Sections 2, 3, 4, 5, and 7

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 clone.2: Document that clone silently ignores CLONE_PID and CLONE_STOPPED

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.

---
 man2/clone.2 | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)
man2/clone.2 +4 -2
index 91c3684..10cef7d 100644
@@ -534,7 +534,8 @@ 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.
+It disappeared in Linux 2.5.16.  Since then, the kernel silently ignores it
+without error.
 .TP
 .BR CLONE_PTRACE " (since Linux 2.2)"
 If
@@ -599,7 +600,8 @@ This flag was
 from Linux 2.6.25 onward,
 and was
 .I removed
-altogether in Linux 2.6.38.
+altogether in Linux 2.6.38.  Since then, the kernel silently ignores it without
+error.
 .\" glibc 2.8 removed this defn from bits/sched.h
 .TP
 .BR CLONE_SYSVSEM " (since Linux 2.5.10)"
Signature · 6 lines
2.1.4

--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
#1 lore raw
Quoted 3 lines · Josh Triplett

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.

Cheers,

Michael

Quoted 30 lines
---
 man2/clone.2 | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)
man2/clone.2 +4 -2
index 91c3684..10cef7d 100644
@@ -534,7 +534,8 @@ 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.
+It disappeared in Linux 2.5.16.  Since then, the kernel silently ignores it
+without error.
 .TP
 .BR CLONE_PTRACE " (since Linux 2.2)"
 If
@@ -599,7 +600,8 @@ This flag was
 from Linux 2.6.25 onward,
 and was
 .I removed
-altogether in Linux 2.6.38.
+altogether in Linux 2.6.38.  Since then, the kernel silently ignores it without
+error.
 .\" glibc 2.8 removed this defn from bits/sched.h
 .TP
 .BR CLONE_SYSVSEM " (since Linux 2.5.10)"
Signature · 7 lines
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

A message that is not in the archive (sent off-list or not yet received): [email protected]

#3 lore raw
Quoted 6 lines · Michael Kerrisk (man-pages)
Quoted 3 lines · Josh Triplett

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.

- Josh Triplett
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html

#4 lore raw
Quoted 9 lines · On 27 February 2015 at 17:31, <[email protected]>…
Quoted 6 lines · Michael Kerrisk (man-pages)
Quoted 3 lines · Josh Triplett

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.)

Cheers,

Michael

Signature · 7 lines
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

A message that is not in the archive (sent off-list or not yet received): CAKgNAkjCvzeo+tHUW+mwL+ptdCX7k=j8fmRX6OtLfFM9HVXJjQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org

#6 lore raw
Quoted 7 lines · Michael Kerrisk (man-pages)
Quoted 6 lines · On 27 February 2015 at 17:31, <[email protected]>…
Quoted 5 lines · Michael Kerrisk (man-pages)
Quoted 3 lines · Josh Triplett

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.

Quoted 5 lines
Quoted 3 lines
Quoted 1 line

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.)

- Josh Triplett
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html

#7 lore raw

Hi Josh,

Quoted 12 lines · On 03/02/2015 05:40 PM, [email protected] wrote:
Quoted 11 lines · Michael Kerrisk (man-pages)
Quoted 9 lines · On 27 February 2015 at 17:31, <[email protected]>…
Quoted 6 lines · Michael Kerrisk (man-pages)
Quoted 3 lines · Josh Triplett

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.

Quoted 8 lines
Quoted 1 line

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.)

Cheers,

Michael

Signature · 7 lines
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

A message that is not in the archive (sent off-list or not yet received): [email protected]

#9 lore raw
Quoted 19 lines · Michael Kerrisk (man-pages)

Hi Josh,

Quoted 16 lines · On 03/02/2015 05:40 PM, [email protected] wrote:
Quoted 7 lines · Michael Kerrisk (man-pages)
Quoted 6 lines · On 27 February 2015 at 17:31, <[email protected]>…
Quoted 5 lines · Michael Kerrisk (man-pages)
Quoted 3 lines · Josh Triplett

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.

Quoted 5 lines
Quoted 3 lines
Quoted 1 line

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.

Quoted 8 lines
Quoted 4 lines

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 [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html