|| ||David Singleton <firstname.lastname@example.org>|
|| ||Robust Futex patches available|
|| ||Tue, 22 Nov 2005 12:38:44 -0800|
|| ||Ingo Molnar <email@example.com>, firstname.lastname@example.org|
There are two new patches for Robust Futex support available at
patch-2.6.14-rt13-rf3 fixes two locking bugs which caused hangs and
patch-2.6.14-rt13-rf4 adds support for pthread_mutexes 'malloc'ed on
I'd also like some advice on the direction POSIX is heading with
robust pthread_mutexes and priority inheritance.
It appears there are some not used openposix tests that use
different flags for
defining robustness. Here is a snip from the openposix robust
Robust Mutex Tests
The tests are under <rtnptl-tests>/robust_test directory.
rt-nptl supports 'robust' behavior, there will be two robust modes,
one is PTHREAD_MUTEX_ROBUST_NP mode, the other is
PTHREAD_MUTEX_ROBUST_SUN_NP mode. When the owner of a mutex dies in
the first mode, the waiter will set the mutex to ENOTRECOVERABLE
state, while in the second mode, the waiter needs to call
pthread_mutex_setconsistency_np to change the state manually.
Currently the PTHREAD_MUTEX_ROBUST_NP is providing
the fucntionality described by the PTHREAD_MUTEX_ROBUST_SUN_NP.
Any advice on which way we should go? I feel we should follow
POSIX and provide both methods and the new pthread_mutex_setconsistency_np
function which provides the mutex recovery mechanism.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/