Home • About Us • A-Z Index • Search * Contact Us • Register • Login • Press • Shop

The Open Brand -- Problem Reporting and Interpretations System

Problem Report 1074 Details

Help Show help | Quick Search | Submit a Test Suite Support Request | Click here to view your privileges

This page provides all information on Problem Report 1074.

Report 1074 Actions

    Problem Report Number 1074
    Submitter's Classification Test Suite problem
    State Resolved
    Resolution Test Suite Deficiency (TSD)
    Problem Resolution ID TSD.X.0530
    Raised 1970-01-01 08:00
    Updated 2003-03-13 08:00
    Published 1999-01-28 08:00
    Product Standard Internationalised System Calls and Libraries Extended V2 (UNIX 98)
    Certification Program The Open Brand certification program
    Test Suite VSRT version 5.0.2
    Test Identification rt.os/aio/aio_read 12
    Problem Summary TSD4R.00010 This test should not be applicable to files that do not support seeking.
    Problem Text
    This request addresses the following results:

    /tset/rt.os/aio/aio_read/T.aio_read 12 Failed
    /tset/rt.os/aio/aio_write/T.aio_write 13 Failed
    /tset/rt.os/aio/lio_listio/T.lio_listio 37 Failed
    /tset/rt.os/aio/lio_listio/T.lio_listio 41 Failed

    This request addresses only the failures in the "pipe" and "pty" cases.

    In each case, the suite is starting an operation with aio_offset
    set to -1, expecting the operation to return -1 and set errno to EINVAL.
    Our implementation ignores aio_offset in this case if the selected device
    is not capable of seeking.

    aio_offset is described on p. 40 of XSH5.2:

    ...the requested operation tales place at the absolute position in the
    file as given by aio_offset, as if lseek() were called immediately
    prior to the operation...

    The behavior of lseek on devices incapable of seeking, such as pipes and
    pty's, is implementation dependent (XSH5.2, p. 489). The behaviour of
    aio_offset on such devices must be implementation dependent as well, and
    cannot be the basis of a standards distinction.
    Test Output

    ************************************************************************
    /tset/rt.os/aio/aio_read/T.aio_read 12 Failed

    Test Description:
    If _POSIX_ASYNCHRONOUS_IO is defined or the implementation supports
    the aio_read() function as described in System Interfaces and Headers,
    Issue 5:
    When the offset implied by aiocbp->aio_offset would be invalid,
    either:
    the aio_read() function shall return -1 and set errno to EINVAL
    or
    the return status of the asynchronous operation shall be set to -1
    and its error status shall be set to EINVAL.

    Test Information:
    > test with file
    For offset -1, request did not fail immediately and aio_error returned 0
    (NO ERROR), expected EINVAL
    For offset -1, request did not fail immediately and aio_return returned
    0, expected -1
    > test with pipe
    For offset -1, request did not fail immediately and aio_error returned 0
    (NO ERROR), expected EINVAL
    For offset -1, request did not fail immediately and aio_return returned
    0, expected -1
    > test with pty
    For offset -1, request did not fail immediately and aio_error returned 0
    (NO ERROR), expected EINVAL
    For offset -1, request did not fail immediately and aio_return returned
    0, expected -1
    > test with tty
    tty testing not configured

    ************************************************************************

    ************************************************************************
    /tset/rt.os/aio/aio_write/T.aio_write 13 Failed

    Test Description:
    If _POSIX_ASYNCHRONOUS_IO is defined or the implementation supports
    the aio_write() function as described in System Interfaces and
    Headers, Issue 5:
    When the offset implied by aiocbp->aio_offset would be invalid,
    either:
    the aio_write() function shall return -1 and set errno to EINVAL
    or
    the return status of the asynchronous operation shall be set to -1
    and its error status shall be set to EINVAL.

    Test Information:
    > test with file
    For offset -1, aio_error returned 0 (NO ERROR), expected EINVAL
    For offset -1, aio_return returned 0, expected -1
    > test with pipe
    For offset -1, aio_error returned 0 (NO ERROR), expected EINVAL
    For offset -1, aio_return returned 0, expected -1
    > test with pty
    For offset -1, aio_error returned 0 (NO ERROR), expected EINVAL
    For offset -1, aio_return returned 0, expected -1
    > test with tty
    tty testing not configured

    ************************************************************************

    ************************************************************************
    /tset/rt.os/aio/lio_listio/T.lio_listio 37 Failed

    Test Description:
    If _POSIX_ASYNCHRONOUS_IO is defined or the implementation supports
    the lio_listio() function as described in System Interfaces and
    Headers, Issue 5:
    On a call to lio_listio() when list[n]->aio_lio_opcode is LIO_READ
    and the offset implied by list[n]->aio_offset would be invalid the
    return status of the asynchronous operation shall be set to -1 and
    its error status shall be set to EINVAL.

    Test Information:
    > test with file
    > test with pipe
    Error status for read is 11 (EAGAIN), expected EINVAL
    > test with pty
    Error status for read is 11 (EAGAIN), expected EINVAL
    > test with tty
    tty testing not configured

    ************************************************************************

    ************************************************************************
    /tset/rt.os/aio/lio_listio/T.lio_listio 41 Failed

    Test Description:
    If _POSIX_ASYNCHRONOUS_IO is defined or the implementation supports
    the lio_listio() function as described in System Interfaces and
    Headers, Issue 5:
    On a call to lio_listio() when list[n].aio_lio_opcode is LIO_WRITE
    and the offset implied by list[n]->aio_offset would be invalid the
    return status of the asynchronous operation shall be set to -1 and
    its error status shall be set to EINVAL.

    Test Information:
    > test with file
    > test with pipe
    lio_listio succeeded
    Error status for write is 0 (NO ERROR), expected EINVAL
    aio_return returned 1 for write, expected -1
    > test with pty
    lio_listio succeeded
    Error status for write is 0 (NO ERROR), expected EINVAL
    aio_return returned 1 for write, expected -1
    > test with tty
    tty testing not configured

    ************************************************************************

    Review Information

    Review Type TSMA Review
    Start Date null
    Completed null
    Status Complete
    Review Recommendation No Resolution Given
    Review Response
    We agree this is a test suite deficiency in the test suite version(s) listed.

    Review Type SA Review
    Start Date null
    Completed null
    Status Complete
    Review Resolution Test Suite Deficiency (TSD)
    Review Conclusion
    This is an agreed Test Suite Deficiency.

    Problem Reporting System Options:

     

    Back   

Contact the Certification Authority