[lkml]   [2005]   [Nov]   [18]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: PI BUG with -rt13

    * david singleton <> 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

    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2005-11-18 18:47    [W:0.022 / U:3.308 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site