View Issue Details

IDProjectCategoryView StatusLast Update
00003171003.1(2004)/Issue 6System Interfacespublic2013-04-16 13:06
Reporterajosey Assigned Toajosey  
PrioritynormalSeverityObjectionTypeError
Status ClosedResolutionAccepted 
NameAndrew Josey
OrganizationThe Open Group
User ReferenceXSHbug2.txt Enhancement Request Number 247
Sectionaio_write
Page Number118
Line Number4335
Interp StatusApproved
Final Accepted Text0000317:0000554
Summary0000317: aio_write append
DescriptionThe aio_write() description states:

    "If O_APPEND is set for the file descriptor, write operations
    append to the file in the same order as the calls were made."

which appears to require strict ordering in all circumstances.
However, this conflicts with section 2.8.2 which states (line 1714):

    "If O_APPEND is set for the file descriptor, or if aio_fildes is
    associated with a device that is incapable of seeking, write
    operations append to the file in the same order as the calls were
    made, with the following exception: under implementation-defined
    circumstances, such as operation on a multi-processor or when
    requests of differing priorities are submitted at the same time,
    the ordering restriction may be relaxed."

The aio_write() description should be updated to match 2.8.2
(preferably by means of a reference to 2.8.2 rather than duplication).
Desired Action    "If O_APPEND is set for the file descriptor, write operations
    append to the file in the same order as the calls were made."

to

    "If O_APPEND is set for the file descriptor, or if aio_fildes is
    associated with a device that is incapable of seeking, write
    operations append to the file in the same order as the calls were
    made, except under circumstances described in [xref to 2.8.2]."

Tagstc1-2008

Activities

ajosey

2010-09-17 08:40

manager   bugnote:0000554

Interpretation response
------------------------

The standard is unclear on this issue, and no conformance
distinction can be made between alternative implementations based
on this. This is being referred to the sponsor.

Rationale:
None.

Notes to the Editor (not part of this interpretation):
-------------------------------------------------------
Make the changes proposed in the Desired action

Issue History

Date Modified Username Field Change
2010-09-17 08:37 ajosey New Issue
2010-09-17 08:37 ajosey Status New => Under Review
2010-09-17 08:37 ajosey Assigned To => ajosey
2010-09-17 08:37 ajosey Name => Andrew Josey
2010-09-17 08:37 ajosey Organization => The Open Group
2010-09-17 08:37 ajosey User Reference => XSHbug2.txt Enhancement Request Number 247
2010-09-17 08:37 ajosey Section => aio_write
2010-09-17 08:37 ajosey Page Number => 118
2010-09-17 08:37 ajosey Line Number => 4335
2010-09-17 08:37 ajosey Interp Status => ---
2010-09-17 08:40 ajosey Note Added: 0000554
2010-09-17 08:41 ajosey Interp Status --- => Proposed
2010-09-17 08:41 ajosey Final Accepted Text => 0000317:0000554
2010-09-17 08:41 ajosey Status Under Review => Interpretation Required
2010-09-17 08:41 ajosey Resolution Open => Accepted
2010-09-17 08:41 ajosey Tag Attached: tc1-2008
2010-11-11 17:25 ajosey Interp Status Proposed => Approved
2013-04-16 13:06 ajosey Status Interpretation Required => Closed