> Now there is a different solution to that problem. Do not look at the > user space value at all and enforce a lookup of possibly available > pi_state. If pi_state can be found, then the new incoming locker T3 > blocks on that pi_state and legitimately races with T2 to acquire the > rt_mutex and the pi_state and therefor the proper ownership of the > user space futex.
That works. Thanks for the detailed explanation too. -- http://siddhesh.in -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
