clone.2: Clarify differences between clone2() syscall and wrapper function

Reported-by: Mike Frysinger <vapier@gentoo.org>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>

diff --git a/man2/clone.2 b/man2/clone.2
index c8cfcf4fa1300a461f9bc762dda7e861b304d38d..bab9a5e6df44167b44a8ff528d43fc5b946a252a 100644 (file)
--- a/man2/clone.2
+++ b/man2/clone.2
@@ -989,7 +989,7 @@ On i386,
 should not be called through vsyscall, but directly through
 .IR "int $0x80" .
 
-On ia64, a different system call is used:
+On ia64, a different interface is used:
 .nf
 
 .BI "int __clone2(int (*" "fn" ")(void *), "
@@ -999,9 +999,19 @@ On ia64, a different system call is used:
 ", pid_t *" ctid " */ );"
 .fi
 .PP
-The
+The prototype shown above is for the glibc wrapper function;
+the raw system call interface has no
+.I fn
+or
+.I arg
+argument, and changes the order of the arguments so that
+.I flags
+is the first argument, and
+.I tls
+is the last argument.
+.PP
 .BR __clone2 ()
-system call operates in the same way as
+operates in the same way as
 .BR clone (),
 except that
 .I child_stack_base