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

The Open Brand -- Problem Reporting and Interpretations System

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

Report 2091 Actions

    Problem Report Number 2091
    Submitter's Classification Test Suite problem
    State Resolved
    Resolution Test Suite Deficiency (TSD)
    Problem Resolution ID TSD.X.1062
    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 VSTH version 5.2.1
    Test Identification PTHR.os/mutex/pthread_mutex_unlock 5
    Problem Summary TSD5TH.00082 The tests fail because the test binaries are not created setuid root, therefore the real time scheduling class cannot be used. If the test binaries are made setuid root, the tests run properly and pas...
    Problem Text

    The tests fail because the test binaries are not created
    setuid root, therefore the real time scheduling class




    cannot be used.

    If the test binaries are made setuid root, the tests run
    properly and pass.

    Test Output
    *************************************************************************************
    /tset/PTHR.os/mutex/pthread_mutex_unlock/T.pthread_mutex_unlock 5 Failed

    Test Information:
    If _POSIX_THREAD_PRIORITY_SCHEDULING is defined,
    when threads executing with the scheduling policy SCHED_FIFO or
    SCHED_RR are waiting on a mutex,
    then they shall acquire the mutex
    in priority order when the mutex is unlocked.
    Posix Ref: Component PTHREAD_MUTEX_UNLOCK
    Assertion 9945-1:1996 13.5.1.2-5(C)
    Unexpected runorder 3 for thread 1




    Unexpected runorder 4 for thread 2
    Unexpected runorder 5 for thread 3
    Unexpected runorder 6 for thread 4
    Unexpected runorder 7 for thread 6
    *****************************************************************************

    *****************************************************************************
    /tset/PTHR.os/rwlock/pthread_rwlock_unlock/T.pthread_rwlock_unlock 2 Failed

    Test Information:
    If _POSIX_THREAD_PRIORITY_SCHEDULING is defined,
    then when a call to pthread_rwlock_unlock(rwlock) results in the
    read-write lock object referenced by rwlock becoming unlocked and there
    are multiple threads waiting to acquire the rwlock for writing,
    then the scheduling policy is used to determine which thread acquires
    the read-write lock object for writing.
    XCAE ref: Component PTHREAD_RWLOCK_UNLOCK
    Assertion 2(C)
    Unexpected lock acquisition order for thread 1
    Unexpected lock acquisition order for thread 2
    Unexpected lock acquisition order for thread 3
    *****************************************************************************

    *****************************************************************************
    /tset/PTHR.os/rwlock/pthread_rwlock_unlock/T.pthread_rwlock_unlock 3 Failed

    Test Information:
    If _POSIX_THREAD_PRIORITY_SCHEDULING is defined,
    then when a call to pthread_rwlock_unlock(rwlock) results in the
    read-write lock object referenced by rwlock becoming unlocked and
    there are multiple threads waiting to acquire the lock for reading,
    then the scheduling policy is used to determine the order in which the
    waiting threads acquire the read-write lock object for reading.
    XCAE ref: Component PTHREAD_RWLOCK_UNLOCK
    Assertion 3(C)
    Unexpected lock acquisition order for thread 1
    Unexpected lock acquisition order for thread 2
    Unexpected lock acquisition order for thread 3
    Unexpected lock acquisition order for thread 4
    Unexpected lock acquisition order for thread 5
    Unexpected lock acquisition order for thread 6
    *****************************************************************************

    Review Information

    Review Type TSMA Review
    Start Date null
    Completed null
    Status Complete
    Review Recommendation No Resolution Given
    Review Response
    A test suite deficiency is recommended.

    The permissions that can be used to change the real time scheduling policies
    are implementation defined, so therefore the code should assume only that
    root has permission to change them.


    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