fork.2: Document fork() behaviour for the Linux native AIO io_context

It was noted on lkml that the fork behaviour is documented
for the POSIX AIO calls, but not for the Linux native calls.
Here is a patch which adds a small blurb that folks will
hopefully find useful.

Upon fork(), the child process does not inherit the
io_context_t data structures returned by io_setup,
and thus cannot submit further asynchronous I/O or
reap event completions for said contexts.

Signed-off-by: Jeff Moyer <jmoyer@redhat.com>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This commit is contained in:
Jeff Moyer 2009-04-27 17:26:27 +12:00 committed by Michael Kerrisk
parent 08eaa638df
commit cb6a78e664
1 changed files with 4 additions and 2 deletions

View File

@ -36,7 +36,7 @@
.\" Greatly expanded, to describe all attributes that differ
.\" parent and child.
.\"
.TH FORK 2 2009-02-04 "Linux" "Linux Programmer's Manual"
.TH FORK 2 2009-04-27 "Linux" "Linux Programmer's Manual"
.SH NAME
fork \- create a child process
.SH SYNOPSIS
@ -83,7 +83,9 @@ The child does not inherit timers from its parent
The child does not inherit outstanding asynchronous I/O operations
from its parent
.RB ( aio_read (3),
.BR aio_write (3)).
.BR aio_write (3)),
nor does it inherit any asynchronous I/O contexts from its parent
.RB ( see io_setup (2)).
.PP
The process attributes in the preceding list are all specified
in POSIX.1-2001.