|
Home About Us A-Z Index Search * Contact Us Register Login Press ShopThe Open Brand -- Problem Reporting and Interpretations System |
Problem Report 2118 Details
Show help | Quick Search | Submit a Test Suite Support Request | Click here to view your privileges
This page provides all information on Problem Report 2118.
Report 2118 Actions
Problem Report Number 2118 Submitter's Classification Test Suite problem State Resolved Resolution Test Suite Deficiency (TSD) Problem Resolution ID TSD.X.1083 Raised 1999-12-22 08:00 Updated 2003-03-13 08:00 Published 1999-12-24 08:00 Product Standard Internationalised System Calls and Libraries Extended V2 (UNIX 98) Certification Program The Open Brand certification program Test Suite VSTH version 5.1.4 Test Identification PTHR.os/all/pthread_mutex_getprioceiling 4 Problem Summary TSD5TH.00076 The test is interrogating an incorrect configuration paramater. In tetexec.cfg we have: # # Does the implementation require appropriate privilege to set the scheduling # priority of a thread to the ma... Problem Text
The test is interrogating an incorrect configuration paramater.
In tetexec.cfg we have:
#
# Does the implementation require appropriate privilege to set the scheduling
# priority of a thread to the maximum supported priority for the
# SCHED_FIFO scheduling policy ?
# Expected range: Y|y|N|n
#
VSTH_SCHED_EPERM=Y
and:
#
# If the implemention requires appropriate privilege to get the
# prioceiling attribute value of a mutex attributes object, then set
# this variable to 'Y' or 'y', otherwise set it to 'N' or 'n'.
# Expected range: |Y|y|N|n
#
VSTH_GPC_EPERM=N
The test interrogates VSTH_SCHED_EPERM.
Our implementation requires appropirate privileges to set the
scheduling priority of a thread to the maximum supported priority for
the SCHED_FIFO scheduling policy, but not to get the prioceiling
attribute value of a mutex attributes object. The test passes if it is
corrected to interrogate VSTH_GPC_EPERM:
---
tset/PTHR.os/all/pthread_mutex_getprioceiling/pthread_mutex_getprioceiling.c
390c397
< p = tet_getvar("VSTH_SCHED_EPERM");
---
> p = tet_getvar("VSTH_GPC_EPERM");Test Output
tset/PTHR.os/all/pthread_mutex_getprioceiling/T.pthread_mutex_getprioceiling #4
200|321 4 20:42:28|TP Start
520|321 4 000324909 1 1|If _POSIX_THREAD_PRIO_PROTECT is defined
520|321 4 000324909 1 2|and the implementation detects that the caller does not
have the
520|321 4 000324909 1 3|privilege to perform the operation:
520|321 4 000324909 1 4|a call to pthread_mutex_getprioceiling(mutex, prioceilin
g) shall
520|321 4 000324909 1 5|fail and return EPERM.
520|321 4 000324909 1 6|Posix Ref: Component PTHREAD_MUTEX_GETPRIOCEILING
520|321 4 000324909 1 7|Assertion 9945-1:1996 13.6.2.4-4(C)
520|321 4 000324910 2 1|pthread_mutex_getprioceiling, expected 0, got 0
520|321 4 000324909 2 1|tet_fork, expected 0, got 1
220|321 4 2 20:42:28|UNRESOLVED
410|321 4 1 20:42:28|IC EndReview 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.
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:
- View Report 2118
- List All PRs
- Search Reports
- Email the System Administrator
- View the The Open Brand Interpretations Database User Manual
Contact the Certification Authority