Bug 2660 - POSIX: case lio_listio/11-1 fails on all arches
Summary: POSIX: case lio_listio/11-1 fails 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-26 06:55 UTC by Kai Kang
Modified: 2012-06-27 02:14 UTC (History)
4 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-26 06:55:24 UTC 
case lio_listio/11-1 fails on all arches

Error message:
lio_listio/11-1.c Error lio_listio() should have returned -1
Comment 1 Kai Kang 2012-06-27 02:14:20 UTC 
Open this bug just to record the case fails, but I think this failure is not a bug.

The case try to:
- open a file for writing                                                   
- submit a list with invalid opcodes to lio_listio in LIO_NOWAIT mode
- check that lio_listio returns -1

The POSIX specification(IEEE Std 1003.1-2008) says（Line 40292）：
The supported operations are LIO_READ, LIO_WRITE, and LIO_NOP

But the spec doesn't say what should happen if the value it not one of the 3 operation codes.

In Khem Raj's <raj.khem@gmail.com> opioion, 
"for aio_lio_opcode posix says "The supported operations are LIO_READ,
LIO_WRITE, and LIO_NOP"

but it does not say what should happen if the value it not one of the above
so IMO its not a bug but falls into undefined behavior."

Ref: http://www.eglibc.org/archives/patches/msg01074.html