As specified in
http://www.opengroup.org/onlinepubs/000095399/functions/pthread_mutexattr_getprioceiling.html, the prioceiling value shall be in range defined by SCHED_FIFO, but
when calling it on a new mutexattr it is zero while the SCHED_FIFO range is
1..99.

The same applies to phtread_mutex_getprioceiling().

This also causes the LTP testsuite to fail.

------- Additional Comment #1 From Petr Baudis 2006-06-19 01:24 -------

Created an attachment (id=1100)
Proposed patch

This patch makes the getprioceiling() functions check if the priority is high
enough and bump it to the minimal allowable priority if not. It is rather ugly
to do the sanitization at that point but the thing is that we default for 0
e.g. in the constant initializers so a pthread_mutexattr_init()-ish solution
isn't really viable. Perhaps we could cache the range, though.

------- Additional Comment #2 From Petr Baudis 2006-06-19 11:10 -------

Adding Jakub Jelinek (the author of implementation of these calls) to Cc.

------- Additional Comment #3 From Petr Baudis 2006-07-12 00:26 -------

So, any thoughts about this?

------- Additional Comment #4 From Ulrich Drepper 2006-08-13 19:38 -------

Fix the test suite.  glibc explicitly announces that priority protection is not
supported.