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

The Open Brand -- Problem Reporting and Interpretations System

Problem Report 1055 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 1055.

Report 1055 Actions

    Problem Report Number 1055
    Submitter's Classification Test Suite problem
    State Resolved
    Resolution Rejected (REJ)
    Problem Resolution ID REJ.X.0292
    Raised 1970-01-01 08:00
    Updated 2003-03-13 08:00
    Published null
    Product Standard Internationalised System Calls and Libraries Extended V2 (UNIX 98)
    Certification Program The Open Brand certification program
    Test Suite VSRT version 5.0.1
    Test Identification rt.os/aio/aio_fsync 1
    Problem Summary PG4R.00012 Some error messages have formats without arguments.
    Problem Text
    The test cases for aio_fsync have invalid print statements to format error
    conditions. The implementation under test detected the failures and upon
    searching the source code five invalid cases exist. Below are the invalid
    journal print statements, the format portion has a "int" (%d) and a
    "string" (%s) conversion modifers which are only two. The format
    contains three values to be printed, "int" i, "int" retval2, and a
    "string" errname(retval2).

    >grep -n "aio_fsync request is not in progress, its error status is %d (%s)"
    aio_fsync.c

    442: in_rpt("aio_fsync request is not in progress, its error status
    is %d (%s)", i, retval2, errname(retval2)); 943: in_rpt("aio_fsync
    request is not in progress, its error status is %d (%s)", i, retval2,
    errname(retval2)); 1378: in_rpt("aio_fsync request is not in
    progress, its error status is %d (%s)", i, retval2, errname(retval2)); 1810:
    in_rpt("aio_fsync request is not in progress, its error status is %d
    (%s)", i, retval2, errname(retval2)); 2330: in_rpt("aio_fsync
    request is not in progress, its error status is %d (%s)", i, retval2,
    errname(retval2));

    The resulting SIGSEGV are due the attempt to print an "int" as a "string".
    It is clear that a missing (%d) was intended to print out the request
    but left out of these statements which should have been coded:

    in_rpt("aio_fsync request %d is not in progress, its error status is %d (%s)",
    i, retval2, errname(retval2));
    Test Output
    10|1 /tset/rt.os/aio/aio_fsync/T.aio_fsync 18:40:27|TC Start, scenario ref
    1-0, ICs: {2,3,4,5} 15|1 3.1-lite 4|TCM Start
    400|1 2 1 18:40:27|IC Start
    200|1 2 18:40:27|TP Start
    520|1 2 00007128 1 1|INFO: No limit on AIO_MAX
    520|1 2 00007128 1 2|> test with pipe
    520|1 2 00007129 1 1|unexpected signal 11 (SIGSEGV) received
    520|1 2 00007128 2 1|> test with pty
    520|1 2 00007128 2 2|pty testing not configured
    520|1 2 00007128 2 3|> test with tty
    520|1 2 00007128 2 4|tty testing not configured
    520|1 2 00007128 2 5|> test with file
    220|1 2 2 18:40:29|UNRESOLVED
    410|1 2 1 18:40:29|IC End
    400|1 3 1 18:40:29|IC Start
    200|1 3 18:40:29|TP Start
    520|1 3 00007128 1 1|INFO: No limit on AIO_MAX
    520|1 3 00007128 1 2|> test with pipe
    520|1 3 00007131 1 1|unexpected signal 11 (SIGSEGV) received
    520|1 3 00007128 2 1|> test with pty
    520|1 3 00007128 2 2|pty testing not configured
    520|1 3 00007128 2 3|> test with tty
    520|1 3 00007128 2 4|tty testing not configured
    520|1 3 00007128 2 5|> test with file
    220|1 3 2 18:40:33|UNRESOLVED
    410|1 3 1 18:40:33|IC End
    400|1 4 1 18:40:33|IC Start
    200|1 4 18:40:33|TP Start
    520|1 4 00007128 1 1|INFO: No limit on AIO_MAX
    520|1 4 00007128 1 2|> test with pipe
    520|1 4 00007133 1 1|unexpected signal 11 (SIGSEGV) received
    520|1 4 00007128 2 1|> test with pty
    520|1 4 00007128 2 2|pty testing not configured
    520|1 4 00007128 2 3|> test with tty
    520|1 4 00007128 2 4|tty testing not configured
    520|1 4 00007128 2 5|> test with file
    520|1 4 00007134 1 1|Expected signal from aio_fsync operation to be received
    after those from aio_reads
    220|1 4 1 18:40:39|FAIL
    410|1 4 1 18:40:39|IC End
    400|1 5 1 18:40:39|IC Start
    200|1 5 18:40:39|TP Start
    520|1 5 00007128 1 1|INFO: No limit on AIO_MAX
    520|1 5 00007128 1 2|> test with pipe
    520|1 5 00007135 1 1|unexpected signal 11 (SIGSEGV) received
    520|1 5 00007128 2 1|> test with pty
    520|1 5 00007128 2 2|pty testing not configured
    520|1 5 00007128 2 3|> test with tty
    520|1 5 00007128 2 4|tty testing not configured
    520|1 5 00007128 2 5|> test with file
    520|1 5 00007136 1 1|Expected si_code for signal 0 = -4, is -2
    520|1 5 00007136 1 2|Expected si_code for signal 1 = -4, is -2
    520|1 5 00007136 1 3|Expected si_code for signal 2 = -4, is -2
    520|1 5 00007136 1 4|Expected si_code for signal 3 = -4, is -2
    520|1 5 00007136 1 5|Expected si_code for signal 4 = -4, is -2
    520|1 5 00007136 1 6|Expected si_code for signal 5 = -4, is -2
    520|1 5 00007136 1 7|Expected si_code for signal 6 = -4, is -2
    520|1 5 00007136 1 8|Expected si_code for signal 7 = -4, is -2
    520|1 5 00007136 1 9|Expected si_code for signal 8 = -4, is -2
    520|1 5 00007136 1 10|Expected si_code for signal 9 = -4, is -2
    520|1 5 00007136 1 11|Expected si_code for signal from aio_fsync = -4, is -2
    220|1 5 1 18:40:45|FAIL
    410|1 5 1 18:40:45|IC End

    Review Information

    Review Type TSMA Review
    Start Date null
    Completed null
    Status Complete
    Review Recommendation No Resolution Given
    Review Response
    This request should be refused.

    The submitter is correct however this should have been filed as an SR not
    an IR.

    These messages are only emitted to illuminate failures due to non-confomring
    implementation behavior. A conforming implementation will not execute
    this code and thus will not encounter problems with these messages.
    As such there is no branding implication here and a TSD would not
    be appropriate.

    These error messages will be corrected in the next release.

    Review Type SA Review
    Start Date null
    Completed null
    Status Complete
    Review Resolution No Resolution Given
    Review Conclusion
    The print statement is not relevant to branding. A new
    request is needed if you wish to justify the fail results.

    Review Type SA Review
    Start Date null
    Completed null
    Status Complete
    Review Resolution Rejected (REJ)
    Review Conclusion
    This request is refused.

    Problem Reporting System Options:

     

    Back   

Contact the Certification Authority