Bug 2666 - POSIX: case aio_error/3-1 return UNRESOLVED on all arches
Summary: POSIX: case aio_error/3-1 return UNRESOLVED on all arches
Status: RESOLVED NOTABUG
Alias: None
Product: Meta-yocto
Classification: Build System, Metadata & Runtime
Component: meta-yocto (show other bugs)
Version: 1.3
Hardware: x86 Multiple
: Undecided enhancement
Target Milestone: ---
Assignee: Kai Kang
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks: 2332
  Show dependency tree
 
Reported: 2012-06-27 06:42 UTC by Kai Kang
Modified: 2012-06-27 06:55 UTC (History)
3 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
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.