Use of the information contained in this unapproved document is at your own risk
.Last update: 10 April,2001
1003.1-96 #118
_____________________________________________________________________________
Interpretation Number: XXXX
Topic: aio_fsync
Relevant Sections: 6.7.9.2 Lines 1252-1265
PASC Interpretation Request: (Defect Report)
----------------------------
Date: 2000 Oct 23
Address details:
IBM Corp.
11400 Burnet Rd MS 9582
Austin TX 78758
512.838.3926
512.838.0735 (fax)
------------------------------------------------------------------------
7 Defect Report concerning (number and title of International Standard
or DIS final text, if applicable):
IEEE Std 1003.1-1996 (incorporates 1003.1-1990, 1003.1b-1993, 1003.1c-1995, 1003.1i-1995) (ISO 9945-1:1996)
------------------------------------------------------------------------
8 Qualifier (e.g. error, omission, clarification required):
3
Error=1 , Omission=2, Clarification=3
------------------------------------------------------------------------
9 References in document (e.g. page, clause, figure, and/or table
numbers):
Sec 6.7.9.2 Lines 1252-1265
------------------------------------------------------------------------
10 Nature of defect (complete, concise explanation of the perceived
problem):
This paragraph describes the aiocbp structure and its uses, in
apparently general terms. It is unclear whether this paragraph
is meant for use in all of the APIs in which aiocbp is used,
or only aio_fsync(). What is unclear in particular, are the
sentences,
"The aio_sigevent member shall determine the asynchronous
notification to occur as specified in 3.3.1.2 when all operations
have achieved synchronous I/O completion. All other members of the
structure referenced by aiocbp are ignored."
1. Does this apply to all of the APIs? It would make implementation
pretty difficult if we can't use the rest of the structure.
2. Does this sentence apply only to aio_fsync(), since the paragraph
is in 6.7.9 and not in a more general section?
3. Does it apply to aio_error() and aio_return()?
------------------------------------------------------------------------
11 Solution proposed by the submitter (optional):
------------------------------------------------------------------------
Interpretation response
------------------------
No this sentence applies only to aio_fsync().
Rationale
-------------
For this function only, only the aio_fildes and aio_sigevent fields
of the AIO control block are used; the rest are ignored since no
seeking , (specific) writing, or reading takes place in this operation.
(source: programming for the real word, POSIX.4, Gallmeister, 1995)
Forwarded to Interpretations group: 31 Oct 2000
Proposed resolution: 15 Feb 2001
Finalised: 15 Mar 2001