Email List: Xaustin-review-lX
[All Lists]

Defect in XSH aio_error()

To: yyyyyyyyyyyyyyy@xxxxxxxxxxxxx
Subject: Defect in XSH aio_error()
From: yyyyyyyy@xxxxxxxxxx
Date: Wed, 1 Oct 2003 13:08:55 +0100 (BST)
        Defect report from : William L. Toth , IBM Austin

(Please direct followup comments direct to yyyyyyyyyyyyyy@xxxxxxxxxxxxx)

@ page 107 line 3959 section aio_error() objection {wlt_vsrt-2}

Problem:

Edition of Specification (Year): 2003

Defect code :  2. Omission

Given the following simplified code, no return value is defined in SUSV3-TC1.

paiocbs[i].aio_lio_opcode = LIO_NOP;
lio_listio(...,&paiocbs,...);
aerr =  aio_error(&paiocbs[i]);

What should aerr equal? A web search showed at least one Unix implementation 
believes EINVAL is the correct return. The spec states that if the AIO 
operation has not yet completed, then aio_error() [EINPROGESS] shall be 
returned. But in this case the operation has not been scheduled, so it will 
never complete, so returning [EINPROGESS] would be misleading.

Action:

return value for this case needs to be explicitly defined.

<Prev in Thread] Current Thread [Next in Thread>
  • Defect in XSH aio_error(), mstrbill <=