lkml.org 
[lkml]   [2017]   [Mar]   [7]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH -v5 12/14] futex,rt_mutex: Restructure rt_mutex_finish_proxy_lock()
On Sat, 4 Mar 2017, Peter Zijlstra wrote:
> +/**
> + * rt_mutex_cleanup_proxy_lock() - Cleanup failed lock acquisition
> + * @lock: the rt_mutex we were woken on
> + * @waiter: the pre-initialized rt_mutex_waiter
> + *
> + * Clean up the failed lock acquisition as per rt_mutex_wait_proxy_lock().
> + *
> + * Returns:
> + * true - did the cleanup, we done.
> + * false - we acquired the lock after rt_mutex_wait_proxy_lock() returned,
> + * caller should disregards its return value.

Hmm. How would that happen? Magic owner assignement to a non waiter? The
callsite only calls here in the failed case.

I must be missing something

Thanks,

tglx

> + *
> + * Special API call for PI-futex support
> + */
> +bool rt_mutex_cleanup_proxy_lock(struct rt_mutex *lock,
> + struct rt_mutex_waiter *waiter)
> +{
> + bool cleanup = false;
> +
> + raw_spin_lock_irq(&lock->wait_lock);
> + /*
> + * If we acquired the lock, no cleanup required.
> + */
> + if (rt_mutex_owner(lock) != current) {
> + remove_waiter(lock, waiter);
> + fixup_rt_mutex_waiters(lock);
> + cleanup = true;
> + }
> + raw_spin_unlock_irq(&lock->wait_lock);
> +
> + return cleanup;
> +}

\
 
 \ /
  Last update: 2017-03-07 15:51    [W:0.199 / U:0.076 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site