]>
Commit | Line | Data |
---|---|---|
fea681da | 1 | .\" Copyright (c) 1992 Drew Eckhardt <drew@cs.colorado.edu>, March 28, 1992 |
8c7b566c | 2 | .\" and Copyright (c) Michael Kerrisk, 2001, 2002, 2005, 2013 |
2297bf0e | 3 | .\" |
fd0fc519 | 4 | .\" %%%LICENSE_START(GPL_NOVERSION_ONELINE) |
fea681da | 5 | .\" May be distributed under the GNU General Public License. |
fd0fc519 | 6 | .\" %%%LICENSE_END |
dccaff1e | 7 | .\" |
fea681da MK |
8 | .\" Modified by Michael Haardt <michael@moria.de> |
9 | .\" Modified 24 Jul 1993 by Rik Faith <faith@cs.unc.edu> | |
10 | .\" Modified 21 Aug 1994 by Michael Chastain <mec@shell.portal.com>: | |
11 | .\" New man page (copied from 'fork.2'). | |
12 | .\" Modified 10 June 1995 by Andries Brouwer <aeb@cwi.nl> | |
13 | .\" Modified 25 April 1998 by Xavier Leroy <Xavier.Leroy@inria.fr> | |
14 | .\" Modified 26 Jun 2001 by Michael Kerrisk | |
15 | .\" Mostly upgraded to 2.4.x | |
16 | .\" Added prototype for sys_clone() plus description | |
17 | .\" Added CLONE_THREAD with a brief description of thread groups | |
c13182ef | 18 | .\" Added CLONE_PARENT and revised entire page remove ambiguity |
fea681da MK |
19 | .\" between "calling process" and "parent process" |
20 | .\" Added CLONE_PTRACE and CLONE_VFORK | |
21 | .\" Added EPERM and EINVAL error codes | |
fd8a5be4 | 22 | .\" Renamed "__clone" to "clone" (which is the prototype in <sched.h>) |
fea681da | 23 | .\" various other minor tidy ups and clarifications. |
c11b1abf | 24 | .\" Modified 26 Jun 2001 by Michael Kerrisk <mtk.manpages@gmail.com> |
d9bfdb9c | 25 | .\" Updated notes for 2.4.7+ behavior of CLONE_THREAD |
c11b1abf | 26 | .\" Modified 15 Oct 2002 by Michael Kerrisk <mtk.manpages@gmail.com> |
fea681da MK |
27 | .\" Added description for CLONE_NEWNS, which was added in 2.4.19 |
28 | .\" Slightly rephrased, aeb. | |
29 | .\" Modified 1 Feb 2003 - added CLONE_SIGHAND restriction, aeb. | |
30 | .\" Modified 1 Jan 2004 - various updates, aeb | |
0967c11f | 31 | .\" Modified 2004-09-10 - added CLONE_PARENT_SETTID etc. - aeb. |
d9bfdb9c | 32 | .\" 2005-04-12, mtk, noted the PID caching behavior of NPTL's getpid() |
31830ef0 | 33 | .\" wrapper under BUGS. |
fd8a5be4 MK |
34 | .\" 2005-05-10, mtk, added CLONE_SYSVSEM, CLONE_UNTRACED, CLONE_STOPPED. |
35 | .\" 2005-05-17, mtk, Substantially enhanced discussion of CLONE_THREAD. | |
4e836144 | 36 | .\" 2008-11-18, mtk, order CLONE_* flags alphabetically |
82ee147a | 37 | .\" 2008-11-18, mtk, document CLONE_NEWPID |
43ce9dda | 38 | .\" 2008-11-19, mtk, document CLONE_NEWUTS |
667417b3 | 39 | .\" 2008-11-19, mtk, document CLONE_NEWIPC |
cfdc761b | 40 | .\" 2008-11-19, Jens Axboe, mtk, document CLONE_IO |
fea681da | 41 | .\" |
4b8c67d9 | 42 | .TH CLONE 2 2017-09-15 "Linux" "Linux Programmer's Manual" |
fea681da | 43 | .SH NAME |
9b0e0996 | 44 | clone, __clone2 \- create a child process |
fea681da | 45 | .SH SYNOPSIS |
c10859eb | 46 | .nf |
81f10dad | 47 | /* Prototype for the glibc wrapper function */ |
dbfe9c70 | 48 | .PP |
4f71ba5d | 49 | .B #define _GNU_SOURCE |
fea681da | 50 | .B #include <sched.h> |
dbfe9c70 | 51 | .PP |
ff929e3b MK |
52 | .BI "int clone(int (*" "fn" ")(void *), void *" child_stack , |
53 | .BI " int " flags ", void *" "arg" ", ... " | |
dd6d3d2e | 54 | .BI " /* pid_t *" ptid ", void *" newtls \ |
ff929e3b | 55 | ", pid_t *" ctid " */ );" |
dbfe9c70 | 56 | .PP |
2a15a76b | 57 | /* For the prototype of the raw system call, see NOTES */ |
c10859eb | 58 | .fi |
fea681da | 59 | .SH DESCRIPTION |
edcc65ff MK |
60 | .BR clone () |
61 | creates a new process, in a manner similar to | |
fea681da | 62 | .BR fork (2). |
efeece04 | 63 | .PP |
81f10dad | 64 | This page describes both the glibc |
e511ffb6 | 65 | .BR clone () |
e585064b | 66 | wrapper function and the underlying system call on which it is based. |
81f10dad | 67 | The main text describes the wrapper function; |
e585064b | 68 | the differences for the raw system call |
81f10dad | 69 | are described toward the end of this page. |
efeece04 | 70 | .PP |
fea681da MK |
71 | Unlike |
72 | .BR fork (2), | |
81f10dad MK |
73 | .BR clone () |
74 | allows the child process to share parts of its execution context with | |
4ba17a6d | 75 | the calling process, such as the virtual address space, the table of file |
c13182ef MK |
76 | descriptors, and the table of signal handlers. |
77 | (Note that on this manual | |
78 | page, "calling process" normally corresponds to "parent process". | |
79 | But see the description of | |
80 | .B CLONE_PARENT | |
fea681da | 81 | below.) |
efeece04 | 82 | .PP |
1533d242 | 83 | One use of |
edcc65ff | 84 | .BR clone () |
4ba17a6d MK |
85 | is to implement threads: multiple flows of control in a program that |
86 | run concurrently in a shared address space. | |
efeece04 | 87 | .PP |
fea681da | 88 | When the child process is created with |
c13182ef | 89 | .BR clone (), |
7495cbc7 MK |
90 | it commences execution by calling the function pointed to by the argument |
91 | .IR fn . | |
fea681da | 92 | (This differs from |
c13182ef | 93 | .BR fork (2), |
fea681da | 94 | where execution continues in the child from the point |
c13182ef MK |
95 | of the |
96 | .BR fork (2) | |
fea681da MK |
97 | call.) |
98 | The | |
fea681da | 99 | .I arg |
7495cbc7 MK |
100 | argument is passed as the argument of the function |
101 | .IR fn . | |
efeece04 | 102 | .PP |
c13182ef | 103 | When the |
fea681da | 104 | .IR fn ( arg ) |
4ba17a6d | 105 | function returns, the child process terminates. |
c13182ef | 106 | The integer returned by |
fea681da | 107 | .I fn |
4ba17a6d | 108 | is the exit status for the child process. |
c13182ef | 109 | The child process may also terminate explicitly by calling |
fea681da MK |
110 | .BR exit (2) |
111 | or after receiving a fatal signal. | |
efeece04 | 112 | .PP |
fea681da MK |
113 | The |
114 | .I child_stack | |
c13182ef MK |
115 | argument specifies the location of the stack used by the child process. |
116 | Since the child and calling process may share memory, | |
fea681da | 117 | it is not possible for the child process to execute in the |
c13182ef MK |
118 | same stack as the calling process. |
119 | The calling process must therefore | |
fea681da MK |
120 | set up memory space for the child stack and pass a pointer to this |
121 | space to | |
edcc65ff | 122 | .BR clone (). |
5fab2e7c | 123 | Stacks grow downward on all processors that run Linux |
fea681da MK |
124 | (except the HP PA processors), so |
125 | .I child_stack | |
126 | usually points to the topmost address of the memory space set up for | |
127 | the child stack. | |
efeece04 | 128 | .PP |
fea681da MK |
129 | The low byte of |
130 | .I flags | |
fd8a5be4 MK |
131 | contains the number of the |
132 | .I "termination signal" | |
133 | sent to the parent when the child dies. | |
134 | If this signal is specified as anything other than | |
fea681da MK |
135 | .BR SIGCHLD , |
136 | then the parent process must specify the | |
c13182ef MK |
137 | .B __WALL |
138 | or | |
fea681da | 139 | .B __WCLONE |
c13182ef MK |
140 | options when waiting for the child with |
141 | .BR wait (2). | |
fea681da MK |
142 | If no signal is specified, then the parent process is not signaled |
143 | when the child terminates. | |
efeece04 | 144 | .PP |
fea681da | 145 | .I flags |
4ba17a6d | 146 | may also be bitwise-ORed with zero or more of the following constants, |
fd8a5be4 | 147 | in order to specify what is shared between the calling process |
fea681da | 148 | and the child process: |
fea681da | 149 | .TP |
f5dbc7c8 | 150 | .BR CLONE_CHILD_CLEARTID " (since Linux 2.5.49)" |
4ba5392d | 151 | Clear (zero) the child thread ID at the location |
d3dbc9b1 | 152 | .I ctid |
f5dbc7c8 MK |
153 | in child memory when the child exits, and do a wakeup on the futex |
154 | at that address. | |
155 | The address involved may be changed by the | |
156 | .BR set_tid_address (2) | |
157 | system call. | |
158 | This is used by threading libraries. | |
159 | .TP | |
160 | .BR CLONE_CHILD_SETTID " (since Linux 2.5.49)" | |
8ef021ea | 161 | Store the child thread ID at the location |
d3dbc9b1 | 162 | .I ctid |
8ef021ea | 163 | in the child's memory. |
b5da2f91 MK |
164 | The store operation completes before |
165 | .BR clone () | |
166 | returns control to user space. | |
f5dbc7c8 | 167 | .TP |
1603d6a1 | 168 | .BR CLONE_FILES " (since Linux 2.0)" |
fea681da | 169 | If |
f5dbc7c8 MK |
170 | .B CLONE_FILES |
171 | is set, the calling process and the child process share the same file | |
172 | descriptor table. | |
173 | Any file descriptor created by the calling process or by the child | |
174 | process is also valid in the other process. | |
175 | Similarly, if one of the processes closes a file descriptor, | |
176 | or changes its associated flags (using the | |
177 | .BR fcntl (2) | |
178 | .B F_SETFD | |
179 | operation), the other process is also affected. | |
8a76b19e KE |
180 | If a process sharing a file descriptor table calls |
181 | .BR execve (2), | |
182 | its file descriptor table is duplicated (unshared). | |
efeece04 | 183 | .IP |
fea681da | 184 | If |
f5dbc7c8 MK |
185 | .B CLONE_FILES |
186 | is not set, the child process inherits a copy of all file descriptors | |
187 | opened in the calling process at the time of | |
188 | .BR clone (). | |
f5dbc7c8 MK |
189 | Subsequent operations that open or close file descriptors, |
190 | or change file descriptor flags, | |
191 | performed by either the calling | |
192 | process or the child process do not affect the other process. | |
db8ba2b4 MK |
193 | Note, however, |
194 | that the duplicated file descriptors in the child refer to the same open file | |
195 | descriptions as the corresponding file descriptors in the calling process, | |
2433365b | 196 | and thus share file offsets and file status flags (see |
db8ba2b4 | 197 | .BR open (2)). |
fea681da | 198 | .TP |
1603d6a1 | 199 | .BR CLONE_FS " (since Linux 2.0)" |
fea681da MK |
200 | If |
201 | .B CLONE_FS | |
9ee4a2b6 | 202 | is set, the caller and the child process share the same filesystem |
c13182ef | 203 | information. |
9ee4a2b6 | 204 | This includes the root of the filesystem, the current |
c13182ef MK |
205 | working directory, and the umask. |
206 | Any call to | |
fea681da MK |
207 | .BR chroot (2), |
208 | .BR chdir (2), | |
209 | or | |
210 | .BR umask (2) | |
edcc65ff | 211 | performed by the calling process or the child process also affects the |
fea681da | 212 | other process. |
efeece04 | 213 | .IP |
c13182ef | 214 | If |
fea681da | 215 | .B CLONE_FS |
9ee4a2b6 | 216 | is not set, the child process works on a copy of the filesystem |
fea681da | 217 | information of the calling process at the time of the |
edcc65ff | 218 | .BR clone () |
fea681da MK |
219 | call. |
220 | Calls to | |
221 | .BR chroot (2), | |
222 | .BR chdir (2), | |
4ba17a6d | 223 | or |
fea681da MK |
224 | .BR umask (2) |
225 | performed later by one of the processes do not affect the other process. | |
fea681da | 226 | .TP |
a4cc375e | 227 | .BR CLONE_IO " (since Linux 2.6.25)" |
11f27a1c JA |
228 | If |
229 | .B CLONE_IO | |
230 | is set, then the new process shares an I/O context with | |
231 | the calling process. | |
232 | If this flag is not set, then (as with | |
233 | .BR fork (2)) | |
234 | the new process has its own I/O context. | |
efeece04 | 235 | .IP |
11f27a1c | 236 | .\" The following based on text from Jens Axboe |
d1f84ed7 | 237 | The I/O context is the I/O scope of the disk scheduler (i.e., |
11f27a1c JA |
238 | what the I/O scheduler uses to model scheduling of a process's I/O). |
239 | If processes share the same I/O context, | |
240 | they are treated as one by the I/O scheduler. | |
241 | As a consequence, they get to share disk time. | |
242 | For some I/O schedulers, | |
243 | .\" the anticipatory and CFQ scheduler | |
244 | if two processes share an I/O context, | |
245 | they will be allowed to interleave their disk access. | |
246 | If several threads are doing I/O on behalf of the same process | |
247 | .RB ( aio_read (3), | |
248 | for instance), they should employ | |
249 | .BR CLONE_IO | |
250 | to get better I/O performance. | |
251 | .\" with CFQ and AS. | |
efeece04 | 252 | .IP |
11f27a1c JA |
253 | If the kernel is not configured with the |
254 | .B CONFIG_BLOCK | |
255 | option, this flag is a no-op. | |
256 | .TP | |
c5af0674 MK |
257 | .BR CLONE_NEWCGROUP " (since Linux 4.6)" |
258 | Create the process in a new cgroup namespace. | |
259 | If this flag is not set, then (as with | |
260 | .BR fork (2)) | |
261 | the process is created in the same cgroup namespaces as the calling process. | |
262 | This flag is intended for the implementation of containers. | |
efeece04 | 263 | .IP |
c5af0674 | 264 | For further information on cgroup namespaces, see |
b9fe4bc3 | 265 | .BR cgroup_namespaces (7). |
efeece04 | 266 | .IP |
c5af0674 MK |
267 | Only a privileged process |
268 | .RB ( CAP_SYS_ADMIN ) | |
269 | can employ | |
270 | .BR CLONE_NEWCGROUP . | |
271 | .\" | |
272 | .TP | |
8722311b | 273 | .BR CLONE_NEWIPC " (since Linux 2.6.19)" |
667417b3 MK |
274 | If |
275 | .B CLONE_NEWIPC | |
276 | is set, then create the process in a new IPC namespace. | |
277 | If this flag is not set, then (as with | |
06b30458 | 278 | .BR fork (2)), |
667417b3 MK |
279 | the process is created in the same IPC namespace as |
280 | the calling process. | |
0236bea9 | 281 | This flag is intended for the implementation of containers. |
efeece04 | 282 | .IP |
efbfd7ec | 283 | An IPC namespace provides an isolated view of System\ V IPC objects (see |
009a049e MK |
284 | .BR svipc (7)) |
285 | and (since Linux 2.6.30) | |
286 | .\" commit 7eafd7c74c3f2e67c27621b987b28397110d643f | |
287 | .\" https://lwn.net/Articles/312232/ | |
288 | POSIX message queues | |
289 | (see | |
290 | .BR mq_overview (7)). | |
19911fa5 MK |
291 | The common characteristic of these IPC mechanisms is that IPC |
292 | objects are identified by mechanisms other than filesystem | |
293 | pathnames. | |
efeece04 | 294 | .IP |
c440fe01 | 295 | Objects created in an IPC namespace are visible to all other processes |
667417b3 MK |
296 | that are members of that namespace, |
297 | but are not visible to processes in other IPC namespaces. | |
efeece04 | 298 | .IP |
83c1f4b5 | 299 | When an IPC namespace is destroyed |
009a049e | 300 | (i.e., when the last process that is a member of the namespace terminates), |
83c1f4b5 | 301 | all IPC objects in the namespace are automatically destroyed. |
efeece04 | 302 | .IP |
ab5dd83f MK |
303 | Only a privileged process |
304 | .RB ( CAP_SYS_ADMIN ) | |
305 | can employ | |
306 | .BR CLONE_NEWIPC . | |
667417b3 MK |
307 | This flag can't be specified in conjunction with |
308 | .BR CLONE_SYSVSEM . | |
efeece04 | 309 | .IP |
9343f8e7 MK |
310 | For further information on IPC namespaces, see |
311 | .BR namespaces (7). | |
667417b3 | 312 | .TP |
163bf178 | 313 | .BR CLONE_NEWNET " (since Linux 2.6.24)" |
33a0ccb2 | 314 | (The implementation of this flag was completed only |
9108d867 | 315 | by about kernel version 2.6.29.) |
efeece04 | 316 | .IP |
163bf178 MK |
317 | If |
318 | .B CLONE_NEWNET | |
319 | is set, then create the process in a new network namespace. | |
320 | If this flag is not set, then (as with | |
57ef8c39 | 321 | .BR fork (2)) |
163bf178 MK |
322 | the process is created in the same network namespace as |
323 | the calling process. | |
324 | This flag is intended for the implementation of containers. | |
efeece04 | 325 | .IP |
163bf178 MK |
326 | A network namespace provides an isolated view of the networking stack |
327 | (network device interfaces, IPv4 and IPv6 protocol stacks, | |
328 | IP routing tables, firewall rules, the | |
329 | .I /proc/net | |
330 | and | |
331 | .I /sys/class/net | |
332 | directory trees, sockets, etc.). | |
333 | A physical network device can live in exactly one | |
334 | network namespace. | |
6f34a82c MK |
335 | A virtual network |
336 | .RB ( veth (4)) | |
337 | device pair provides a pipe-like abstraction | |
163bf178 MK |
338 | that can be used to create tunnels between network namespaces, |
339 | and can be used to create a bridge to a physical network device | |
340 | in another namespace. | |
efeece04 | 341 | .IP |
bf032425 SH |
342 | When a network namespace is freed |
343 | (i.e., when the last process in the namespace terminates), | |
344 | its physical network devices are moved back to the | |
345 | initial network namespace (not to the parent of the process). | |
73680728 MK |
346 | For further information on network namespaces, see |
347 | .BR namespaces (7). | |
efeece04 | 348 | .IP |
ab5dd83f MK |
349 | Only a privileged process |
350 | .RB ( CAP_SYS_ADMIN ) | |
351 | can employ | |
352 | .BR CLONE_NEWNET . | |
163bf178 | 353 | .TP |
c10859eb | 354 | .BR CLONE_NEWNS " (since Linux 2.4.19)" |
3dd2331c MK |
355 | If |
356 | .B CLONE_NEWNS | |
357 | is set, the cloned child is started in a new mount namespace, | |
358 | initialized with a copy of the namespace of the parent. | |
359 | If | |
fea681da | 360 | .B CLONE_NEWNS |
3dd2331c | 361 | is not set, the child lives in the same mount |
4df2eb09 | 362 | namespace as the parent. |
efeece04 | 363 | .IP |
ab5dd83f MK |
364 | Only a privileged process |
365 | .RB ( CAP_SYS_ADMIN ) | |
366 | can employ | |
367 | .BR CLONE_NEWNS . | |
fea681da MK |
368 | It is not permitted to specify both |
369 | .B CLONE_NEWNS | |
370 | and | |
371 | .B CLONE_FS | |
9219d208 | 372 | .\" See https://lwn.net/Articles/543273/ |
fea681da | 373 | in the same |
e511ffb6 | 374 | .BR clone () |
fea681da | 375 | call. |
efeece04 | 376 | .IP |
c212248c MK |
377 | For further information on mount namespaces, see |
378 | .BR namespaces (7) | |
379 | and | |
380 | .BR mount_namespaces (7). | |
9d005472 MK |
381 | .TP |
382 | .BR CLONE_NEWPID " (since Linux 2.6.24)" | |
383 | .\" This explanation draws a lot of details from | |
384 | .\" http://lwn.net/Articles/259217/ | |
385 | .\" Authors: Pavel Emelyanov <xemul@openvz.org> | |
386 | .\" and Kir Kolyshkin <kir@openvz.org> | |
387 | .\" | |
388 | .\" The primary kernel commit is 30e49c263e36341b60b735cbef5ca37912549264 | |
389 | .\" Author: Pavel Emelyanov <xemul@openvz.org> | |
390 | If | |
391 | .B CLONE_NEWPID | |
392 | is set, then create the process in a new PID namespace. | |
393 | If this flag is not set, then (as with | |
394 | .BR fork (2)) | |
395 | the process is created in the same PID namespace as | |
396 | the calling process. | |
397 | This flag is intended for the implementation of containers. | |
efeece04 | 398 | .IP |
9d005472 | 399 | For further information on PID namespaces, see |
7e0e902b MK |
400 | .BR namespaces (7) |
401 | and | |
39b3f005 | 402 | .BR pid_namespaces (7). |
efeece04 | 403 | .IP |
ab5dd83f MK |
404 | Only a privileged process |
405 | .RB ( CAP_SYS_ADMIN ) | |
406 | can employ | |
407 | .BR CLONE_NEWPID . | |
9d005472 | 408 | This flag can't be specified in conjunction with |
f0007192 MK |
409 | .BR CLONE_THREAD |
410 | or | |
411 | .BR CLONE_PARENT . | |
70d21f17 | 412 | .TP |
06b30458 MK |
413 | .BR CLONE_NEWUSER |
414 | (This flag first became meaningful for | |
415 | .BR clone () | |
4d2b3ed7 MK |
416 | in Linux 2.6.23, |
417 | the current | |
11a38815 | 418 | .BR clone () |
4d2b3ed7 MK |
419 | semantics were merged in Linux 3.5, |
420 | and the final pieces to make the user namespaces completely usable were | |
421 | merged in Linux 3.8.) | |
efeece04 | 422 | .IP |
70d21f17 EB |
423 | If |
424 | .B CLONE_NEWUSER | |
06b30458 MK |
425 | is set, then create the process in a new user namespace. |
426 | If this flag is not set, then (as with | |
57ef8c39 | 427 | .BR fork (2)) |
70d21f17 | 428 | the process is created in the same user namespace as the calling process. |
efeece04 | 429 | .IP |
fefbcba8 MK |
430 | Before Linux 3.8, use of |
431 | .BR CLONE_NEWUSER | |
432 | required that the caller have three capabilities: | |
433 | .BR CAP_SYS_ADMIN , | |
434 | .BR CAP_SETUID , | |
435 | and | |
436 | .BR CAP_SETGID . | |
437 | .\" Before Linux 2.6.29, it appears that only CAP_SYS_ADMIN was needed | |
06b30458 | 438 | Starting with Linux 3.8, |
9d005472 | 439 | no privileges are needed to create a user namespace. |
efeece04 | 440 | .IP |
5e72cf7d MK |
441 | This flag can't be specified in conjunction with |
442 | .BR CLONE_THREAD | |
443 | or | |
444 | .BR CLONE_PARENT . | |
445 | For security reasons, | |
446 | .\" commit e66eded8309ebf679d3d3c1f5820d1f2ca332c71 | |
447 | .\" https://lwn.net/Articles/543273/ | |
448 | .\" The fix actually went into 3.9 and into 3.8.3. However, user namespaces | |
449 | .\" were, for practical purposes, unusable in earlier 3.8.x because of the | |
ab3311aa | 450 | .\" various filesystems that didn't support userns. |
f0007192 MK |
451 | .BR CLONE_NEWUSER |
452 | cannot be specified in conjunction with | |
5e72cf7d | 453 | .BR CLONE_FS . |
efeece04 | 454 | .IP |
5e72cf7d | 455 | For further information on user namespaces, see |
e5f3df48 MK |
456 | .BR namespaces (7) |
457 | and | |
5e72cf7d | 458 | .BR user_namespaces (7). |
82ee147a | 459 | .TP |
43ce9dda MK |
460 | .BR CLONE_NEWUTS " (since Linux 2.6.19)" |
461 | If | |
462 | .B CLONE_NEWUTS | |
e1b11906 MK |
463 | is set, then create the process in a new UTS namespace, |
464 | whose identifiers are initialized by duplicating the identifiers | |
465 | from the UTS namespace of the calling process. | |
43ce9dda | 466 | If this flag is not set, then (as with |
57ef8c39 | 467 | .BR fork (2)) |
43ce9dda MK |
468 | the process is created in the same UTS namespace as |
469 | the calling process. | |
0236bea9 | 470 | This flag is intended for the implementation of containers. |
efeece04 | 471 | .IP |
43ce9dda MK |
472 | A UTS namespace is the set of identifiers returned by |
473 | .BR uname (2); | |
850905cf | 474 | among these, the domain name and the hostname can be modified by |
43ce9dda MK |
475 | .BR setdomainname (2) |
476 | and | |
43ce9dda MK |
477 | .BR sethostname (2), |
478 | respectively. | |
c440fe01 MK |
479 | Changes made to the identifiers in a UTS namespace |
480 | are visible to all other processes in the same namespace, | |
43ce9dda | 481 | but are not visible to processes in other UTS namespaces. |
efeece04 | 482 | .IP |
ab5dd83f MK |
483 | Only a privileged process |
484 | .RB ( CAP_SYS_ADMIN ) | |
485 | can employ | |
486 | .BR CLONE_NEWUTS . | |
efeece04 | 487 | .IP |
83d9e9b2 | 488 | For further information on UTS namespaces, see |
9cc7ad66 | 489 | .BR namespaces (7). |
43ce9dda | 490 | .TP |
f5dbc7c8 MK |
491 | .BR CLONE_PARENT " (since Linux 2.3.12)" |
492 | If | |
493 | .B CLONE_PARENT | |
494 | is set, then the parent of the new child (as returned by | |
495 | .BR getppid (2)) | |
496 | will be the same as that of the calling process. | |
efeece04 | 497 | .IP |
f5dbc7c8 MK |
498 | If |
499 | .B CLONE_PARENT | |
500 | is not set, then (as with | |
501 | .BR fork (2)) | |
502 | the child's parent is the calling process. | |
efeece04 | 503 | .IP |
f5dbc7c8 MK |
504 | Note that it is the parent process, as returned by |
505 | .BR getppid (2), | |
506 | which is signaled when the child terminates, so that | |
507 | if | |
508 | .B CLONE_PARENT | |
509 | is set, then the parent of the calling process, rather than the | |
510 | calling process itself, will be signaled. | |
511 | .TP | |
512 | .BR CLONE_PARENT_SETTID " (since Linux 2.5.49)" | |
8ef021ea | 513 | Store the child thread ID at the location |
d3dbc9b1 | 514 | .I ptid |
8ef021ea | 515 | in the parent's memory. |
f5dbc7c8 MK |
516 | (In Linux 2.5.32-2.5.48 there was a flag |
517 | .B CLONE_SETTID | |
518 | that did this.) | |
b5da2f91 MK |
519 | The store operation completes before |
520 | .BR clone () | |
521 | returns control to user space. | |
f5dbc7c8 | 522 | .TP |
1c173eb3 | 523 | .BR CLONE_PID " (Linux 2.0 to 2.5.15)" |
f5dbc7c8 MK |
524 | If |
525 | .B CLONE_PID | |
526 | is set, the child process is created with the same process ID as | |
527 | the calling process. | |
528 | This is good for hacking the system, but otherwise | |
529 | of not much use. | |
1c173eb3 | 530 | From Linux 2.3.21 onward, this flag could be |
f5dbc7c8 | 531 | specified only by the system boot process (PID 0). |
1c173eb3 MK |
532 | The flag disappeared completely from the kernel sources in Linux 2.5.16. |
533 | Since then, the kernel silently ignores this bit if it is specified in | |
534 | .IR flags . | |
f5dbc7c8 | 535 | .TP |
1603d6a1 | 536 | .BR CLONE_PTRACE " (since Linux 2.2)" |
f5dbc7c8 MK |
537 | If |
538 | .B CLONE_PTRACE | |
539 | is specified, and the calling process is being traced, | |
540 | then trace the child also (see | |
541 | .BR ptrace (2)). | |
542 | .TP | |
543 | .BR CLONE_SETTLS " (since Linux 2.5.32)" | |
dd6d3d2e | 544 | The TLS (Thread Local Storage) descriptor is set to |
2551f801 | 545 | .IR newtls . |
efeece04 | 546 | .IP |
dd6d3d2e KF |
547 | The interpretation of |
548 | .I newtls | |
549 | and the resulting effect is architecture dependent. | |
550 | On x86, | |
f5dbc7c8 | 551 | .I newtls |
dd6d3d2e | 552 | is interpreted as a |
2551f801 | 553 | .IR "struct user_desc\ *" |
35bf8cb4 | 554 | (see |
dd6d3d2e | 555 | .BR set_thread_area (2)). |
9ea5bc66 | 556 | On x86-64 it is the new value to be set for the %fs base register |
35bf8cb4 | 557 | (see the |
2551f801 | 558 | .B ARCH_SET_FS |
dd6d3d2e KF |
559 | argument to |
560 | .BR arch_prctl (2)). | |
561 | On architectures with a dedicated TLS register, it is the new value | |
562 | of that register. | |
f5dbc7c8 | 563 | .TP |
1603d6a1 | 564 | .BR CLONE_SIGHAND " (since Linux 2.0)" |
fea681da MK |
565 | If |
566 | .B CLONE_SIGHAND | |
314c8ff4 | 567 | is set, the calling process and the child process share the same table of |
c13182ef MK |
568 | signal handlers. |
569 | If the calling process or child process calls | |
fea681da | 570 | .BR sigaction (2) |
c13182ef MK |
571 | to change the behavior associated with a signal, the behavior is |
572 | changed in the other process as well. | |
573 | However, the calling process and child | |
fea681da | 574 | processes still have distinct signal masks and sets of pending |
c13182ef | 575 | signals. |
4ba17a6d | 576 | So, one of them may block or unblock signals using |
fea681da MK |
577 | .BR sigprocmask (2) |
578 | without affecting the other process. | |
efeece04 | 579 | .IP |
fea681da MK |
580 | If |
581 | .B CLONE_SIGHAND | |
582 | is not set, the child process inherits a copy of the signal handlers | |
583 | of the calling process at the time | |
edcc65ff | 584 | .BR clone () |
c13182ef MK |
585 | is called. |
586 | Calls to | |
fea681da MK |
587 | .BR sigaction (2) |
588 | performed later by one of the processes have no effect on the other | |
589 | process. | |
efeece04 | 590 | .IP |
29546c24 MK |
591 | Since Linux 2.6.0-test6, |
592 | .I flags | |
593 | must also include | |
594 | .B CLONE_VM | |
595 | if | |
596 | .B CLONE_SIGHAND | |
597 | is specified | |
fea681da | 598 | .TP |
a69b6bda MK |
599 | .BR CLONE_STOPPED " (since Linux 2.6.0-test2)" |
600 | If | |
601 | .B CLONE_STOPPED | |
602 | is set, then the child is initially stopped (as though it was sent a | |
603 | .B SIGSTOP | |
604 | signal), and must be resumed by sending it a | |
605 | .B SIGCONT | |
606 | signal. | |
efeece04 | 607 | .IP |
a60450a9 MK |
608 | This flag was |
609 | .I deprecated | |
610 | from Linux 2.6.25 onward, | |
611 | and was | |
612 | .I removed | |
28b44abc MK |
613 | altogether in Linux 2.6.38. |
614 | Since then, the kernel silently ignores it without error. | |
a5a061ee | 615 | .\" glibc 2.8 removed this defn from bits/sched.h |
c5af0674 MK |
616 | Starting with Linux 4.6, the same bit was reused for the |
617 | .BR CLONE_NEWCGROUP | |
618 | flag. | |
a69b6bda | 619 | .TP |
f5dbc7c8 | 620 | .BR CLONE_SYSVSEM " (since Linux 2.5.10)" |
fea681da | 621 | If |
f5dbc7c8 MK |
622 | .B CLONE_SYSVSEM |
623 | is set, then the child and the calling process share | |
5ada4b94 MK |
624 | a single list of System V semaphore adjustment |
625 | .RI ( semadj ) | |
626 | values (see | |
f5dbc7c8 | 627 | .BR semop (2)). |
5ada4b94 MK |
628 | In this case, the shared list accumulates |
629 | .I semadj | |
630 | values across all processes sharing the list, | |
631 | and semaphore adjustments are performed only when the last process | |
632 | that is sharing the list terminates (or ceases sharing the list using | |
633 | .BR unshare (2)). | |
f5d401dd | 634 | If this flag is not set, then the child has a separate |
5ada4b94 MK |
635 | .I semadj |
636 | list that is initially empty. | |
fea681da MK |
637 | .TP |
638 | .BR CLONE_THREAD " (since Linux 2.4.0-test8)" | |
639 | If | |
640 | .B CLONE_THREAD | |
641 | is set, the child is placed in the same thread group as the calling process. | |
fd8a5be4 MK |
642 | To make the remainder of the discussion of |
643 | .B CLONE_THREAD | |
644 | more readable, the term "thread" is used to refer to the | |
645 | processes within a thread group. | |
efeece04 | 646 | .IP |
fd8a5be4 MK |
647 | Thread groups were a feature added in Linux 2.4 to support the |
648 | POSIX threads notion of a set of threads that share a single PID. | |
649 | Internally, this shared PID is the so-called | |
650 | thread group identifier (TGID) for the thread group. | |
c13182ef | 651 | Since Linux 2.4, calls to |
fea681da | 652 | .BR getpid (2) |
fd8a5be4 | 653 | return the TGID of the caller. |
efeece04 | 654 | .IP |
fd8a5be4 MK |
655 | The threads within a group can be distinguished by their (system-wide) |
656 | unique thread IDs (TID). | |
657 | A new thread's TID is available as the function result | |
658 | returned to the caller of | |
659 | .BR clone (), | |
660 | and a thread can obtain | |
661 | its own TID using | |
662 | .BR gettid (2). | |
efeece04 | 663 | .IP |
c13182ef | 664 | When a call is made to |
fd8a5be4 MK |
665 | .BR clone () |
666 | without specifying | |
667 | .BR CLONE_THREAD , | |
668 | then the resulting thread is placed in a new thread group | |
669 | whose TGID is the same as the thread's TID. | |
670 | This thread is the | |
671 | .I leader | |
672 | of the new thread group. | |
efeece04 | 673 | .IP |
fd8a5be4 MK |
674 | A new thread created with |
675 | .B CLONE_THREAD | |
676 | has the same parent process as the caller of | |
677 | .BR clone () | |
c13182ef | 678 | (i.e., like |
fd8a5be4 MK |
679 | .BR CLONE_PARENT ), |
680 | so that calls to | |
681 | .BR getppid (2) | |
682 | return the same value for all of the threads in a thread group. | |
683 | When a | |
c13182ef | 684 | .B CLONE_THREAD |
fd8a5be4 MK |
685 | thread terminates, the thread that created it using |
686 | .BR clone () | |
687 | is not sent a | |
688 | .B SIGCHLD | |
689 | (or other termination) signal; | |
690 | nor can the status of such a thread be obtained | |
691 | using | |
692 | .BR wait (2). | |
693 | (The thread is said to be | |
694 | .IR detached .) | |
efeece04 | 695 | .IP |
e2fbf61d MK |
696 | After all of the threads in a thread group terminate |
697 | the parent process of the thread group is sent a | |
fd8a5be4 MK |
698 | .B SIGCHLD |
699 | (or other termination) signal. | |
efeece04 | 700 | .IP |
fd8a5be4 MK |
701 | If any of the threads in a thread group performs an |
702 | .BR execve (2), | |
703 | then all threads other than the thread group leader are terminated, | |
704 | and the new program is executed in the thread group leader. | |
efeece04 | 705 | .IP |
f7110f60 MK |
706 | If one of the threads in a thread group creates a child using |
707 | .BR fork (2), | |
708 | then any thread in the group can | |
709 | .BR wait (2) | |
710 | for that child. | |
efeece04 | 711 | .IP |
edcc65ff | 712 | Since Linux 2.5.35, |
fd8a5be4 MK |
713 | .I flags |
714 | must also include | |
715 | .B CLONE_SIGHAND | |
716 | if | |
717 | .B CLONE_THREAD | |
6fd69f33 MK |
718 | is specified |
719 | (and note that, since Linux 2.6.0-test6, | |
720 | .BR CLONE_SIGHAND | |
721 | also requires | |
722 | .BR CLONE_VM | |
723 | to be included). | |
efeece04 | 724 | .IP |
e2fbf61d MK |
725 | Signals may be sent to a thread group as a whole (i.e., a TGID) using |
726 | .BR kill (2), | |
727 | or to a specific thread (i.e., TID) using | |
728 | .BR tgkill (2). | |
efeece04 | 729 | .IP |
e2fbf61d MK |
730 | Signal dispositions and actions are process-wide: |
731 | if an unhandled signal is delivered to a thread, then | |
732 | it will affect (terminate, stop, continue, be ignored in) | |
733 | all members of the thread group. | |
efeece04 | 734 | .IP |
99408a60 | 735 | Each thread has its own signal mask, as set by |
e2fbf61d | 736 | .BR sigprocmask (2), |
82a06020 | 737 | but signals can be pending either: for the whole process |
e2fbf61d MK |
738 | (i.e., deliverable to any member of the thread group), |
739 | when sent with | |
82a06020 | 740 | .BR kill (2); |
e2fbf61d MK |
741 | or for an individual thread, when sent with |
742 | .BR tgkill (2). | |
99408a60 MK |
743 | A call to |
744 | .BR sigpending (2) | |
745 | returns a signal set that is the union of the signals pending for the | |
746 | whole process and the signals that are pending for the calling thread. | |
efeece04 | 747 | .IP |
c13182ef | 748 | If |
e2fbf61d MK |
749 | .BR kill (2) |
750 | is used to send a signal to a thread group, | |
751 | and the thread group has installed a handler for the signal, then | |
752 | the handler will be invoked in exactly one, arbitrarily selected | |
753 | member of the thread group that has not blocked the signal. | |
c13182ef | 754 | If multiple threads in a group are waiting to accept the same signal using |
e2fbf61d MK |
755 | .BR sigwaitinfo (2), |
756 | the kernel will arbitrarily select one of these threads | |
c13182ef | 757 | to receive a signal sent using |
e2fbf61d | 758 | .BR kill (2). |
a69b6bda | 759 | .TP |
f5dbc7c8 | 760 | .BR CLONE_UNTRACED " (since Linux 2.5.46)" |
a69b6bda | 761 | If |
f5dbc7c8 MK |
762 | .B CLONE_UNTRACED |
763 | is specified, then a tracing process cannot force | |
764 | .B CLONE_PTRACE | |
765 | on this child process. | |
fea681da | 766 | .TP |
1603d6a1 | 767 | .BR CLONE_VFORK " (since Linux 2.2)" |
f5dbc7c8 MK |
768 | If |
769 | .B CLONE_VFORK | |
770 | is set, the execution of the calling process is suspended | |
771 | until the child releases its virtual memory | |
772 | resources via a call to | |
773 | .BR execve (2) | |
774 | or | |
775 | .BR _exit (2) | |
776 | (as with | |
777 | .BR vfork (2)). | |
efeece04 | 778 | .IP |
f5dbc7c8 MK |
779 | If |
780 | .B CLONE_VFORK | |
4b4a853a | 781 | is not set, then both the calling process and the child are schedulable |
f5dbc7c8 MK |
782 | after the call, and an application should not rely on execution occurring |
783 | in any particular order. | |
fea681da | 784 | .TP |
1603d6a1 | 785 | .BR CLONE_VM " (since Linux 2.0)" |
f5dbc7c8 MK |
786 | If |
787 | .B CLONE_VM | |
788 | is set, the calling process and the child process run in the same memory | |
789 | space. | |
790 | In particular, memory writes performed by the calling process | |
791 | or by the child process are also visible in the other process. | |
792 | Moreover, any memory mapping or unmapping performed with | |
793 | .BR mmap (2) | |
794 | or | |
795 | .BR munmap (2) | |
796 | by the child or calling process also affects the other process. | |
efeece04 | 797 | .IP |
f5dbc7c8 MK |
798 | If |
799 | .B CLONE_VM | |
800 | is not set, the child process runs in a separate copy of the memory | |
801 | space of the calling process at the time of | |
802 | .BR clone (). | |
803 | Memory writes or file mappings/unmappings performed by one of the | |
804 | processes do not affect the other, as with | |
805 | .BR fork (2). | |
1874193e | 806 | .SH NOTES |
1c6ebc4b MK |
807 | Note that the glibc |
808 | .BR clone () | |
809 | wrapper function makes some changes | |
810 | in the memory pointed to by | |
811 | .I child_stack | |
812 | (changes required to set the stack up correctly for the child) | |
813 | .I before | |
814 | invoking the | |
815 | .BR clone () | |
816 | system call. | |
817 | So, in cases where | |
818 | .BR clone () | |
819 | is used to recursively create children, | |
820 | do not use the buffer employed for the parent's stack | |
821 | as the stack of the child. | |
822 | .\" | |
0722a578 | 823 | .SS C library/kernel differences |
e585064b MK |
824 | The raw |
825 | .BR clone () | |
fea681da MK |
826 | system call corresponds more closely to |
827 | .BR fork (2) | |
828 | in that execution in the child continues from the point of the | |
c13182ef | 829 | call. |
5add3af3 MK |
830 | As such, the |
831 | .I fn | |
c13182ef | 832 | and |
5add3af3 MK |
833 | .I arg |
834 | arguments of the | |
835 | .BR clone () | |
836 | wrapper function are omitted. | |
161fce30 | 837 | .PP |
b219e68c | 838 | Another difference for the raw |
d35f5c34 | 839 | .BR clone () |
b219e68c MK |
840 | system call is that the |
841 | .I child_stack | |
82f9cb98 | 842 | argument may be NULL, |
b219e68c MK |
843 | in which case the child uses a duplicate of the parent's stack. |
844 | (Copy-on-write semantics ensure that the child gets separate copies | |
845 | of stack pages when either process modifies the stack.) | |
846 | In this case, for correct operation, the | |
847 | .B CLONE_VM | |
848 | option should not be specified. | |
d35f5c34 MK |
849 | (If the child |
850 | .I shares | |
851 | the parent's memory because of the use of the | |
852 | .BR CLONE_VM | |
b219e68c MK |
853 | flag, |
854 | then no copy-on-write duplication occurs and chaos is likely to result.) | |
d35f5c34 | 855 | .PP |
161fce30 MK |
856 | The order of the arguments also differs in the raw system call, |
857 | and there are variations in the arguments across architectures, | |
858 | as detailed in the following paragraphs. | |
efeece04 | 859 | .PP |
2a15a76b | 860 | The raw system call interface on x86-64 and some other architectures |
6bd80e8b | 861 | (including sh, tile, and alpha) is: |
efeece04 | 862 | .PP |
5add3af3 | 863 | .in +4 |
b76974c1 | 864 | .EX |
2a15a76b MK |
865 | .BI "long clone(unsigned long " flags ", void *" child_stack , |
866 | .BI " int *" ptid ", int *" ctid , | |
867 | .BI " unsigned long " newtls ); | |
b76974c1 | 868 | .EE |
2a15a76b | 869 | .in |
efeece04 | 870 | .PP |
2a15a76b MK |
871 | On x86-32, and several other common architectures |
872 | (including score, ARM, ARM 64, PA-RISC, arc, Power PC, xtensa, | |
873 | and MIPS), | |
874 | .\" CONFIG_CLONE_BACKWARDS | |
875 | the order of the last two arguments is reversed: | |
efeece04 | 876 | .PP |
2a15a76b | 877 | .in +4 |
b76974c1 | 878 | .EX |
5add3af3 | 879 | .BI "long clone(unsigned long " flags ", void *" child_stack , |
2a15a76b MK |
880 | .BI " int *" ptid ", unsigned long " newtls , |
881 | .BI " int *" ctid ); | |
b76974c1 | 882 | .EE |
2a15a76b | 883 | .in |
efeece04 | 884 | .PP |
2a15a76b MK |
885 | On the cris and s390 architectures, |
886 | .\" CONFIG_CLONE_BACKWARDS2 | |
887 | the order of the first two arguments is reversed: | |
efeece04 | 888 | .PP |
2a15a76b | 889 | .in +4 |
b76974c1 | 890 | .EX |
2a15a76b | 891 | .BI "long clone(void *" child_stack ", unsigned long " flags , |
fda55470 | 892 | .BI " int *" ptid ", int *" ctid , |
dd6d3d2e | 893 | .BI " unsigned long " newtls ); |
b76974c1 | 894 | .EE |
2a15a76b | 895 | .in |
efeece04 | 896 | .PP |
2a15a76b MK |
897 | On the microblaze architecture, |
898 | .\" CONFIG_CLONE_BACKWARDS3 | |
899 | an additional argument is supplied: | |
efeece04 | 900 | .PP |
2a15a76b | 901 | .in +4 |
b76974c1 | 902 | .EX |
2a15a76b MK |
903 | .BI "long clone(unsigned long " flags ", void *" child_stack , |
904 | .BI " int " stack_size , "\fR /* Size of stack */" | |
905 | .BI " int *" ptid ", int *" ctid , | |
906 | .BI " unsigned long " newtls ); | |
b76974c1 | 907 | .EE |
5add3af3 | 908 | .in |
2a15a76b | 909 | .\" |
251113d0 | 910 | .SS blackfin, m68k, and sparc |
2a15a76b MK |
911 | .\" Mike Frysinger noted in a 2013 mail: |
912 | .\" these arches don't define __ARCH_WANT_SYS_CLONE: | |
913 | .\" blackfin ia64 m68k sparc | |
251113d0 | 914 | The argument-passing conventions on |
04346be5 | 915 | blackfin, m68k, and sparc are different from the descriptions above. |
251113d0 | 916 | For details, see the kernel (and glibc) source. |
574c92b6 | 917 | .SS ia64 |
097a1f3b | 918 | On ia64, a different interface is used: |
7a346077 | 919 | .PP |
097a1f3b | 920 | .nf |
097a1f3b MK |
921 | .BI "int __clone2(int (*" "fn" ")(void *), " |
922 | .BI " void *" child_stack_base ", size_t " stack_size , | |
923 | .BI " int " flags ", void *" "arg" ", ... " | |
924 | .BI " /* pid_t *" ptid ", struct user_desc *" tls \ | |
925 | ", pid_t *" ctid " */ );" | |
926 | .fi | |
927 | .PP | |
928 | The prototype shown above is for the glibc wrapper function; | |
929 | the raw system call interface has no | |
930 | .I fn | |
931 | or | |
932 | .I arg | |
933 | argument, and changes the order of the arguments so that | |
934 | .I flags | |
935 | is the first argument, and | |
936 | .I tls | |
937 | is the last argument. | |
938 | .PP | |
939 | .BR __clone2 () | |
940 | operates in the same way as | |
941 | .BR clone (), | |
942 | except that | |
943 | .I child_stack_base | |
944 | points to the lowest address of the child's stack area, | |
945 | and | |
946 | .I stack_size | |
947 | specifies the size of the stack pointed to by | |
948 | .IR child_stack_base . | |
5add3af3 | 949 | .SS Linux 2.4 and earlier |
577f9b62 MK |
950 | In Linux 2.4 and earlier, |
951 | .BR clone () | |
952 | does not take arguments | |
953 | .IR ptid , | |
954 | .IR tls , | |
955 | and | |
130b2e49 | 956 | .IR ctid . |
47297adb | 957 | .SH RETURN VALUE |
0bfa087b MK |
958 | .\" gettid(2) returns current->pid; |
959 | .\" getpid(2) returns current->tgid; | |
fea681da | 960 | On success, the thread ID of the child process is returned |
c13182ef | 961 | in the caller's thread of execution. |
84811e86 | 962 | On failure, \-1 is returned |
fea681da MK |
963 | in the caller's context, no child process will be created, and |
964 | .I errno | |
965 | will be set appropriately. | |
fea681da MK |
966 | .SH ERRORS |
967 | .TP | |
968 | .B EAGAIN | |
e1b6e186 MK |
969 | Too many processes are already running; see |
970 | .BR fork (2). | |
fea681da MK |
971 | .TP |
972 | .B EINVAL | |
973 | .B CLONE_SIGHAND | |
974 | was specified, but | |
975 | .B CLONE_VM | |
2e8a7fb3 MK |
976 | was not. |
977 | (Since Linux 2.6.0-test6.) | |
fea681da MK |
978 | .TP |
979 | .B EINVAL | |
980 | .B CLONE_THREAD | |
981 | was specified, but | |
982 | .B CLONE_SIGHAND | |
6387216b MK |
983 | was not. |
984 | (Since Linux 2.5.35.) | |
29546c24 MK |
985 | .\" .TP |
986 | .\" .B EINVAL | |
987 | .\" Precisely one of | |
988 | .\" .B CLONE_DETACHED | |
989 | .\" and | |
990 | .\" .B CLONE_THREAD | |
6387216b MK |
991 | .\" was specified. |
992 | .\" (Since Linux 2.6.0-test6.) | |
fea681da MK |
993 | .TP |
994 | .B EINVAL | |
d34e5645 | 995 | .\" commit e66eded8309ebf679d3d3c1f5820d1f2ca332c71 |
fea681da MK |
996 | Both |
997 | .B CLONE_FS | |
998 | and | |
999 | .B CLONE_NEWNS | |
1000 | were specified in | |
1001 | .IR flags . | |
1002 | .TP | |
d34e5645 MK |
1003 | .BR EINVAL " (since Linux 3.9)" |
1004 | Both | |
1005 | .B CLONE_NEWUSER | |
1006 | and | |
1007 | .B CLONE_FS | |
1008 | were specified in | |
1009 | .IR flags . | |
1010 | .TP | |
fea681da | 1011 | .B EINVAL |
82ee147a | 1012 | Both |
667417b3 MK |
1013 | .B CLONE_NEWIPC |
1014 | and | |
1015 | .B CLONE_SYSVSEM | |
1016 | were specified in | |
1017 | .IR flags . | |
1018 | .TP | |
1019 | .B EINVAL | |
f0007192 | 1020 | One (or both) of |
82ee147a | 1021 | .BR CLONE_NEWPID |
f0007192 MK |
1022 | or |
1023 | .BR CLONE_NEWUSER | |
1024 | and one (or both) of | |
82ee147a | 1025 | .BR CLONE_THREAD |
f0007192 MK |
1026 | or |
1027 | .BR CLONE_PARENT | |
82ee147a MK |
1028 | were specified in |
1029 | .IR flags . | |
1030 | .TP | |
1031 | .B EINVAL | |
d4748fad | 1032 | Returned by the glibc |
edcc65ff | 1033 | .BR clone () |
d4748fad MK |
1034 | wrapper function when |
1035 | .IR fn | |
1036 | or | |
1037 | .IR child_stack | |
1038 | is specified as NULL. | |
fea681da | 1039 | .TP |
28cad2c1 | 1040 | .B EINVAL |
667417b3 MK |
1041 | .BR CLONE_NEWIPC |
1042 | was specified in | |
1043 | .IR flags , | |
1044 | but the kernel was not configured with the | |
1045 | .B CONFIG_SYSVIPC | |
1046 | and | |
1047 | .BR CONFIG_IPC_NS | |
1048 | options. | |
1049 | .TP | |
1050 | .B EINVAL | |
163bf178 MK |
1051 | .BR CLONE_NEWNET |
1052 | was specified in | |
1053 | .IR flags , | |
1054 | but the kernel was not configured with the | |
1055 | .B CONFIG_NET_NS | |
1056 | option. | |
1057 | .TP | |
1058 | .B EINVAL | |
28cad2c1 MK |
1059 | .BR CLONE_NEWPID |
1060 | was specified in | |
1061 | .IR flags , | |
1062 | but the kernel was not configured with the | |
1063 | .B CONFIG_PID_NS | |
1064 | option. | |
1065 | .TP | |
43ce9dda | 1066 | .B EINVAL |
231d0bbe MK |
1067 | .BR CLONE_NEWUSER |
1068 | was specified in | |
1069 | .IR flags , | |
1070 | but the kernel was not configured with the | |
1071 | .B CONFIG_USER_NS | |
1072 | option. | |
1073 | .TP | |
1074 | .B EINVAL | |
43ce9dda MK |
1075 | .BR CLONE_NEWUTS |
1076 | was specified in | |
1077 | .IR flags , | |
1078 | but the kernel was not configured with the | |
832fe8ea | 1079 | .B CONFIG_UTS_NS |
43ce9dda MK |
1080 | option. |
1081 | .TP | |
c550a897 MK |
1082 | .B EINVAL |
1083 | .I child_stack | |
1084 | is not aligned to a suitable boundary for this architecture. | |
1085 | For example, on aarch64, | |
1086 | .I child_stack | |
1087 | must be a multiple of 16. | |
1088 | .TP | |
fea681da MK |
1089 | .B ENOMEM |
1090 | Cannot allocate sufficient memory to allocate a task structure for the | |
1091 | child, or to copy those parts of the caller's context that need to be | |
1092 | copied. | |
1093 | .TP | |
b20e22ae MK |
1094 | .BR ENOSPC " (since Linux 3.7)" |
1095 | .\" commit f2302505775fd13ba93f034206f1e2a587017929 | |
1096 | .B CLONE_NEWPID | |
1097 | was specified in flags, | |
1098 | but the limit on the nesting depth of PID namespaces | |
1099 | would have been exceeded; see | |
1100 | .BR pid_namespaces (7). | |
1101 | .TP | |
b5742ecc MK |
1102 | .BR ENOSPC " (since Linux 4.9; beforehand " EUSERS ) |
1103 | .B CLONE_NEWUSER | |
1104 | was specified in | |
1105 | .IR flags , | |
1106 | and the call would cause the limit on the number of | |
1107 | nested user namespaces to be exceeded. | |
1108 | See | |
1109 | .BR user_namespaces (7). | |
efeece04 | 1110 | .IP |
b5742ecc MK |
1111 | From Linux 3.11 to Linux 4.8, the error diagnosed in this case was |
1112 | .BR EUSERS . | |
1113 | .TP | |
2f7a331e MK |
1114 | .BR ENOSPC " (since Linux 4.9)" |
1115 | One of the values in | |
1116 | .I flags | |
1117 | specified the creation of a new user namespace, | |
1118 | but doing so would have caused the limit defined by the corresponding file in | |
1119 | .IR /proc/sys/user | |
1120 | to be exceeded. | |
1121 | For further details, see | |
1122 | .BR namespaces (7). | |
1123 | .TP | |
fea681da | 1124 | .B EPERM |
aa825b59 | 1125 | .BR CLONE_NEWCGROUP , |
667417b3 | 1126 | .BR CLONE_NEWIPC , |
163bf178 | 1127 | .BR CLONE_NEWNET , |
43ce9dda MK |
1128 | .BR CLONE_NEWNS , |
1129 | .BR CLONE_NEWPID , | |
82ee147a | 1130 | or |
43ce9dda | 1131 | .BR CLONE_NEWUTS |
00b08db3 | 1132 | was specified by an unprivileged process (process without \fBCAP_SYS_ADMIN\fP). |
fea681da MK |
1133 | .TP |
1134 | .B EPERM | |
1135 | .B CLONE_PID | |
1136 | was specified by a process other than process 0. | |
1c173eb3 | 1137 | (This error occurs only on Linux 2.5.15 and earlier.) |
365d292a MK |
1138 | .TP |
1139 | .B EPERM | |
1140 | .BR CLONE_NEWUSER | |
1141 | was specified in | |
1142 | .IR flags , | |
1143 | but either the effective user ID or the effective group ID of the caller | |
1144 | does not have a mapping in the parent namespace (see | |
f58fb24f | 1145 | .BR user_namespaces (7)). |
6fd119e7 | 1146 | .TP |
ac007938 MK |
1147 | .BR EPERM " (since Linux 3.9)" |
1148 | .\" commit 3151527ee007b73a0ebd296010f1c0454a919c7d | |
11a38815 AM |
1149 | .B CLONE_NEWUSER |
1150 | was specified in | |
ac007938 MK |
1151 | .I flags |
1152 | and the caller is in a chroot environment | |
1153 | .\" FIXME What is the rationale for this restriction? | |
1154 | (i.e., the caller's root directory does not match the root directory | |
1155 | of the mount namespace in which it resides). | |
1156 | .TP | |
6717ee86 MK |
1157 | .BR ERESTARTNOINTR " (since Linux 2.6.17)" |
1158 | .\" commit 4a2c7a7837da1b91468e50426066d988050e4d56 | |
1159 | System call was interrupted by a signal and will be restarted. | |
1160 | (This can be seen only during a trace.) | |
1161 | .TP | |
b5742ecc | 1162 | .BR EUSERS " (Linux 3.11 to Linux 4.8)" |
6fd119e7 MK |
1163 | .B CLONE_NEWUSER |
1164 | was specified in | |
1165 | .IR flags , | |
b5742ecc MK |
1166 | and the limit on the number of nested user namespaces would be exceeded. |
1167 | See the discussion of the | |
1168 | .BR ENOSPC | |
1169 | error above. | |
92b72224 MK |
1170 | .\" .SH VERSIONS |
1171 | .\" There is no entry for | |
1172 | .\" .BR clone () | |
1173 | .\" in libc5. | |
1174 | .\" glibc2 provides | |
1175 | .\" .BR clone () | |
1176 | .\" as described in this manual page. | |
47297adb | 1177 | .SH CONFORMING TO |
a1d5f77c | 1178 | .BR clone () |
e585064b | 1179 | is Linux-specific and should not be used in programs |
a1d5f77c | 1180 | intended to be portable. |
fea681da | 1181 | .SH NOTES |
79bdcc4a MK |
1182 | The |
1183 | .BR kcmp (2) | |
1184 | system call can be used to test whether two processes share various | |
49dba87f | 1185 | resources such as a file descriptor table, |
79bdcc4a | 1186 | System V semaphore undo operations, or a virtual address space. |
efeece04 MK |
1187 | .PP |
1188 | .PP | |
c471c363 MK |
1189 | Handlers registered using |
1190 | .BR pthread_atfork (3) | |
1191 | are not executed during a call to | |
1192 | .BR clone (). | |
efeece04 | 1193 | .PP |
ca8b1e32 | 1194 | In the Linux 2.4.x series, |
fd8a5be4 MK |
1195 | .B CLONE_THREAD |
1196 | generally does not make the parent of the new thread the same | |
1197 | as the parent of the calling process. | |
1198 | However, for kernel versions 2.4.7 to 2.4.18 the | |
1199 | .B CLONE_THREAD | |
1200 | flag implied the | |
c13182ef | 1201 | .B CLONE_PARENT |
ca8b1e32 | 1202 | flag (as in Linux 2.6.0 and later). |
efeece04 | 1203 | .PP |
c13182ef MK |
1204 | For a while there was |
1205 | .B CLONE_DETACHED | |
a5053dcb | 1206 | (introduced in 2.5.32): |
c13182ef | 1207 | parent wants no child-exit signal. |
4d543007 | 1208 | In Linux 2.6.2, the need to give this flag together with |
c13182ef | 1209 | .B CLONE_THREAD |
a5053dcb MK |
1210 | disappeared. |
1211 | This flag is still defined, but has no effect. | |
efeece04 | 1212 | .PP |
34ccb744 | 1213 | On i386, |
a5a997ca MK |
1214 | .BR clone () |
1215 | should not be called through vsyscall, but directly through | |
1216 | .IR "int $0x80" . | |
31830ef0 | 1217 | .SH BUGS |
abcf3b1d MK |
1218 | GNU C library versions 2.3.4 up to and including 2.24 |
1219 | contained a wrapper function for | |
0bfa087b | 1220 | .BR getpid (2) |
abcf3b1d MK |
1221 | that performed caching of PIDs. |
1222 | This caching relied on support in the glibc wrapper for | |
c60237c9 | 1223 | .BR clone (), |
abcf3b1d MK |
1224 | but limitations in the implementation |
1225 | meant that the cache was not up to date in some circumstances. | |
c60237c9 | 1226 | In particular, |
abcf3b1d | 1227 | if a signal was delivered to the child immediately after the |
c60237c9 MK |
1228 | .BR clone () |
1229 | call, then a call to | |
0b80cf56 | 1230 | .BR getpid (2) |
abcf3b1d | 1231 | in a handler for the signal could return the PID |
c60237c9 | 1232 | of the calling process ("the parent"), |
abcf3b1d | 1233 | if the clone wrapper had not yet had a chance to update the PID |
c60237c9 MK |
1234 | cache in the child. |
1235 | (This discussion ignores the case where the child was created using | |
9291ce36 | 1236 | .BR CLONE_THREAD , |
c60237c9 | 1237 | when |
0b80cf56 | 1238 | .BR getpid (2) |
c60237c9 MK |
1239 | .I should |
1240 | return the same value in the child and in the process that called | |
1241 | .BR clone (), | |
a1d48abb | 1242 | since the caller and the child are in the same thread group. |
e7d807b7 | 1243 | The stale-cache problem also does not occur if the |
a1d48abb JR |
1244 | .I flags |
1245 | argument includes | |
1246 | .BR CLONE_VM .) | |
abcf3b1d MK |
1247 | To get the truth, it was sometimes necessary to use code such as the following: |
1248 | .PP | |
47f743f1 MK |
1249 | .in +4n |
1250 | .EX | |
1251 | #include <syscall.h> | |
31830ef0 | 1252 | |
47f743f1 | 1253 | pid_t mypid; |
31830ef0 | 1254 | |
47f743f1 MK |
1255 | mypid = syscall(SYS_getpid); |
1256 | .EE | |
1257 | .in | |
c60237c9 MK |
1258 | .\" See also the following bug reports |
1259 | .\" https://bugzilla.redhat.com/show_bug.cgi?id=417521 | |
1260 | .\" http://sourceware.org/bugzilla/show_bug.cgi?id=6910 | |
abcf3b1d MK |
1261 | .PP |
1262 | Because of the stale-cache problem, as well as other problems noted in | |
1263 | .BR getpid (2), | |
1264 | the PID caching feature was removed in glibc 2.25. | |
8c7b566c | 1265 | .SH EXAMPLE |
8c7b566c | 1266 | The following program demonstrates the use of |
9c13072a | 1267 | .BR clone () |
8c7b566c MK |
1268 | to create a child process that executes in a separate UTS namespace. |
1269 | The child changes the hostname in its UTS namespace. | |
1270 | Both parent and child then display the system hostname, | |
1271 | making it possible to see that the hostname | |
1272 | differs in the UTS namespaces of the parent and child. | |
1273 | For an example of the use of this program, see | |
1274 | .BR setns (2). | |
f30b7415 | 1275 | .SS Program source |
e7d0bb47 | 1276 | .EX |
8c7b566c MK |
1277 | #define _GNU_SOURCE |
1278 | #include <sys/wait.h> | |
1279 | #include <sys/utsname.h> | |
1280 | #include <sched.h> | |
1281 | #include <string.h> | |
1282 | #include <stdio.h> | |
1283 | #include <stdlib.h> | |
1284 | #include <unistd.h> | |
1285 | ||
1286 | #define errExit(msg) do { perror(msg); exit(EXIT_FAILURE); \\ | |
1287 | } while (0) | |
1288 | ||
1289 | static int /* Start function for cloned child */ | |
1290 | childFunc(void *arg) | |
1291 | { | |
1292 | struct utsname uts; | |
1293 | ||
1294 | /* Change hostname in UTS namespace of child */ | |
1295 | ||
1296 | if (sethostname(arg, strlen(arg)) == \-1) | |
1297 | errExit("sethostname"); | |
1298 | ||
07d4e6ea | 1299 | /* Retrieve and display hostname */ |
8c7b566c MK |
1300 | |
1301 | if (uname(&uts) == \-1) | |
1302 | errExit("uname"); | |
1303 | printf("uts.nodename in child: %s\\n", uts.nodename); | |
1304 | ||
1305 | /* Keep the namespace open for a while, by sleeping. | |
1306 | This allows some experimentation\-\-for example, another | |
1307 | process might join the namespace. */ | |
9f1b9726 | 1308 | |
8c7b566c MK |
1309 | sleep(200); |
1310 | ||
1311 | return 0; /* Child terminates now */ | |
1312 | } | |
1313 | ||
1314 | #define STACK_SIZE (1024 * 1024) /* Stack size for cloned child */ | |
1315 | ||
1316 | int | |
1317 | main(int argc, char *argv[]) | |
1318 | { | |
1319 | char *stack; /* Start of stack buffer */ | |
1320 | char *stackTop; /* End of stack buffer */ | |
1321 | pid_t pid; | |
1322 | struct utsname uts; | |
1323 | ||
1324 | if (argc < 2) { | |
1325 | fprintf(stderr, "Usage: %s <child\-hostname>\\n", argv[0]); | |
1326 | exit(EXIT_SUCCESS); | |
1327 | } | |
1328 | ||
1329 | /* Allocate stack for child */ | |
1330 | ||
1331 | stack = malloc(STACK_SIZE); | |
1332 | if (stack == NULL) | |
1333 | errExit("malloc"); | |
1334 | stackTop = stack + STACK_SIZE; /* Assume stack grows downward */ | |
1335 | ||
1336 | /* Create child that has its own UTS namespace; | |
1337 | child commences execution in childFunc() */ | |
1338 | ||
1339 | pid = clone(childFunc, stackTop, CLONE_NEWUTS | SIGCHLD, argv[1]); | |
1340 | if (pid == \-1) | |
1341 | errExit("clone"); | |
1342 | printf("clone() returned %ld\\n", (long) pid); | |
1343 | ||
1344 | /* Parent falls through to here */ | |
1345 | ||
1346 | sleep(1); /* Give child time to change its hostname */ | |
1347 | ||
9f1b9726 | 1348 | /* Display hostname in parent\(aqs UTS namespace. This will be |
8c7b566c MK |
1349 | different from hostname in child\(aqs UTS namespace. */ |
1350 | ||
1351 | if (uname(&uts) == \-1) | |
1352 | errExit("uname"); | |
1353 | printf("uts.nodename in parent: %s\\n", uts.nodename); | |
1354 | ||
1355 | if (waitpid(pid, NULL, 0) == \-1) /* Wait for child */ | |
1356 | errExit("waitpid"); | |
1357 | printf("child has terminated\\n"); | |
1358 | ||
1359 | exit(EXIT_SUCCESS); | |
1360 | } | |
e7d0bb47 | 1361 | .EE |
47297adb | 1362 | .SH SEE ALSO |
fea681da | 1363 | .BR fork (2), |
2b44301c | 1364 | .BR futex (2), |
fea681da MK |
1365 | .BR getpid (2), |
1366 | .BR gettid (2), | |
6f8746e4 | 1367 | .BR kcmp (2), |
f2d0bbf1 | 1368 | .BR set_thread_area (2), |
2b44301c | 1369 | .BR set_tid_address (2), |
8403481f | 1370 | .BR setns (2), |
f2d0bbf1 | 1371 | .BR tkill (2), |
5cc01e9c | 1372 | .BR unshare (2), |
fea681da | 1373 | .BR wait (2), |
3616b7c0 | 1374 | .BR capabilities (7), |
41096af1 | 1375 | .BR namespaces (7), |
3616b7c0 | 1376 | .BR pthreads (7) |