Bug 2665

Summary: POSIX: case aio_return 2-1 3-2 4-1 return UNRESOLVED on all arches
Product: [Build System, Metadata & Runtime] Meta-yocto Reporter: Kai Kang <kai.kang>
Component: meta-yoctoAssignee: Kai Kang <kai.kang>
Status: VERIFIED NOTABUG QA Contact:
Severity: enhancement    
Priority: Undecided CC: laurentiu.serban, poky.bs.watcher, poky.watcher, zhenfeng.zhao
Version: 1.3   
Target Milestone: 1.3 M2   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: ---
Bug Depends on:    
Bug Blocks: 2332    

Description Kai Kang 2012-06-27 03:26:57 UTC 
case aio_return 2-1 3-2 4-1 return UNRESOLVED on all arches
case 2-1 and 3-2 call aio_return 2 times and expect return -1
case 4-1 call aio_return with argument aiocbp which does not point at a control block for an asynchronous I/O request, and expect error EINVAL
Comment 1 Kai Kang 2012-06-27 03:34:17 UTC 
For case 2-1 3-2, they test call aio_return 2 times and expect return -1. 

In the POSIX spec, it says:
The aio_return( ) function may be called exactly once to retrieve the
return status of a given asynchronous operation; thereafter, if the same aiocb structure is used in
a call to aio_return( ) or aio_error( ), an error *may* be returned.

It just says "may" and not compel to return an error, so it is implement dependent and I think they are not bugs.

---------------------------------------------
For case 4-1, the spec says:

The aio_return() function *may* fail if:

[EINVAL]  The aiocbp argument does not refer to an asynchronous operation whose
          return status has not yet been retrieved.

This is also 'may' and is implement dependent and not a bug.
Comment 2 Laurentiu Serban 2012-07-31 08:26:12 UTC 
Setting to Verified after last comment