Bug 2666

Summary: POSIX: case aio_error/3-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: RESOLVED NOTABUG QA Contact:
Severity: enhancement    
Priority: Undecided CC: poky.bs.watcher, poky.watcher, zhenfeng.zhao
Version: 1.3   
Target Milestone: ---   
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 06:42:26 UTC 
case aio_error 3-1 return UNRESOLVED on all arches

Similiar to aio_return/4-1, it try to call aio_error 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 06:55:33 UTC 
The POSIX spec says about aio_error:

ERRORS
The aio_error( ) function may fail if:
[EINVAL]   The aiocbp argument does not refer to an asynchronous operation whose
           return status has not yet been retrieved.

It just say "may" and not a compelling contraint, so I think this is implement dependent and not a bug.