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

The Open Brand -- Problem Reporting and Interpretations System

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

Report 2401 Actions

    Problem Report Number 2401
    Submitter's Classification Test Suite problem
    State Resolved
    Resolution Test Suite Deficiency (TSD)
    Problem Resolution ID TSD.X.1240
    Raised 2004-06-18 00:10
    Updated 2004-06-23 01:08
    Published 2004-06-23 01:08
    Product Standard Internationalised System Calls and Libraries Extended V2 (UNIX 98)
    Certification Program The Open Brand certification program
    Test Suite VSTH version 5.3.3
    Test Identification PTHR.os/rwlock/pthread_rwlock_tryrdlock/T.pthread_rwlock_tryrdlock 6
    PTHR.os/rwlock/pthread_rwlock_trywrlock/T.pthread_rwlock_trywrlock 5
    Problem Summary Tests assume that if rdlock/rwlock fails with EDEADLK then
    tryrdlock/tryrwlock must also fail with EDEADLK.
    Problem Text For both rdlock/rwlock and tryrdlock/tryrwlock, failing with EDEADLK is
    a "may fail" and not a "will fail".

    The problem with these assertions is that the same configuration
    variable, VSTH_RWL_DEADLK, is used for both the rdlock/rwlock and
    tryrdlock/tryrwlock when the standard does not require that if
    rdlock/rwlock fails with EDEADLK then tryrdlock/tryrwlock must also fail
    with EDEADLK. Further, it would be undesirable for an implementation to
    do so since EDEADLK for trylock was removed from SUSv3 because it was
    agreed that trylock routines should never indicate a deadlock condition.

    The test should have seperate configuration variables for these.
    Test Output
    ****************************************************************************************************************

    /tset/PTHR.os/rwlock/pthread_rwlock_tryrdlock/T.pthread_rwlock_tryrdlock
    6 Failed

    Test Description:
    If the implementation detects that the current thread already
    owns the read-write lock referenced by rwlock for writing:
    a call to pthread_rwlock_tryrdlock(rwlock) shall fail and return
    EDEADLCK.
    XCAE ref: Component PTHREAD_RWLOCK_TRYRDLOCK Assertion 6(C)

    Test Information:
    If the implementation detects that the current thread already
    owns the read-write lock referenced by rwlock for writing:
    a call to pthread_rwlock_tryrdlock(rwlock) shall fail
    and return EDEADLK.
    XCAE ref: Component PTHREAD_RWLOCK_TRYRDLOCK
    Assertion 6(C)
    pthread_rwlock_tryrdlock, expected 45, got 16
    Thread exitval, expected 0, got 2


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


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

    /tset/PTHR.os/rwlock/pthread_rwlock_trywrlock/T.pthread_rwlock_trywrlock
    5 Failed

    Test Description:
    If the implementation detects that the current thread already
    owns
    the read-write lock object referenced by rwlock for reading or
    writing:
    a call to pthread_trywrlock_trywrlock(rwlock) shall fail and
    return EDEADLCK.
    XCAE ref: Component PTHREAD_RWLOCK_TRYWRLOCK Assertion 5(C)

    Test Information:
    If the implementation detects that the current thread already
    owns the read-write lock object referenced by rwlock for
    reading or writing:
    a call to pthread_trywrlock_trywrlock(rwlock) shall fail
    and return EDEADLK.
    XCAE ref: Component PTHREAD_RWLOCK_TRYWRLOCK
    Assertion 5(C)
    pthread_rwlock_trywrlock, expected 45, got 16
    Thread exitval, expected 0, got 2


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

    Review Information

    Review Type TSMA Review
    Start Date 2004-06-18 00:10
    Last Updated 2004-06-18 17:45
    Completed 2004-06-18 17:45
    Status Complete
    Review Recommendation Test Suite Deficiency (TSD)
    Review Response This is accepted as a fault in the test suite.

    Review Type SA Review
    Start Date 2004-06-18 16:45
    Last Updated 2004-06-23 00:49
    Completed 2004-06-23 00:49
    Status Complete
    Review Resolution Test Suite Deficiency (TSD)
    Review Conclusion This PR represents an agreed test suite deficiency

    Problem Reporting System Options:

     

    Back   

Contact the Certification Authority