LDP
/
man-pages
mirror of https://github.com/mkerrisk/man-pages
0
1
Fork 0
Code Releases Activity

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>
This commit is contained in:
Michael Kerrisk 2013-04-16 07:40:12 +02:00
parent e585064bb9
commit 51f1f5d957
1 changed files with 13 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
man2/clone.2
View File

@ -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