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

clone.2: Make the implications of CLONE_FILES more explicit 

If CLONE_FILES is not set, the duplicated FDs nevertheless share
file offset and status flags via the open file description.

Reported-by: Elliott Hughes <enh@google.com>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This commit is contained in:
Michael Kerrisk 2016-08-24 11:35:35 +12:00
parent 6a459f6fee
commit db8ba2b415
1 changed files with 5 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
man2/clone.2
View File

@ -192,14 +192,15 @@ If
is not set, the child process inherits a copy of all file descriptors
opened in the calling process at the time of
.BR clone ().
(The duplicated file descriptors in the child refer to the
same open file descriptions (see
.BR open (2))
as the corresponding file descriptors in the calling process.)
Subsequent operations that open or close file descriptors,
or change file descriptor flags,
performed by either the calling
process or the child process do not affect the other process.
Note, however,
that the duplicated file descriptors in the child refer to the same open file
descriptions as the corresponding file descriptors in the calling process,
and thus share file offsets and files status flags (see
.BR open (2)).
.TP
.BR CLONE_FS " (since Linux 2.0)"
If