Defect in XSH fork()

[yyyyyyy@xxxxxxxxxx]

        Defect report from : Ulrich Drepper , Red Hat, Inc.

(Please direct followup comments direct to yyyyyyyyyyyyyy@xxxxxxxxxxxxx)

@ page 403 line 13030 section fork() objection [ud-fork-aio]

Problem:

Edition of Specification (Year): 2004

Defect code :  2. Omission

The spec says that no AIO request is inherited by the child after fork.
It further says that after fork() and before an exec function only
async-safe interfaces can be called.

Unfortunately aio_error(), aio_return(), and aio_suspend() fall into
this category.  It is OK to call these functions.

What isn't specified is what the state of the aio control blocks is and
therefore how these functions have to behave.


Action:

One possible solution is to declare all control blocks invalid and require that 
EINVAL is returned.  In this case add at the end of line 13030:

All aio control blocks are marked invalid.


Another possibility is that all requeuests are assumed to be canceled.
In this case add at the end of 13030:

All outstanding AIO requests are marked as canceled.