Messages in this thread | | | Date | Fri, 18 Nov 2005 18:44:54 +0100 | From | Ingo Molnar <> | Subject | Re: PI BUG with -rt13 |
| |
* david singleton <dsingleton@mvista.com> wrote:
> >both rt_mutex_free() and rt_mutex_set_owner() must be called with the > >proper locking. David? > > Yes, the lock needs to be protected by the robust semaphore. > The locking order is: > > mmap_sem to protect the vma that holds the pthread_mutex > > robust_sem to protect the futex_mutex chain. > > futex_mutex - the rt_mutex associated with the > pthread_mutex.
well, also lock->wait_lock and lock->pi_lock. The act of making another thread the owner of this particular mutex must be performed carefully. Check out rt.c to see what locking dependencies there are. (We can also do a lockless cmpxchg for unlocked mutexes, under certain circumstances.)
Ingo - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |