提交 85f48961 编写于 作者: M Maarten Lankhorst 提交者: Ingo Molnar

mutex: Fix w/w mutex deadlock injection

The check needs to be for > 1, because ctx->acquired is already incremented.
This will prevent ww_mutex_lock_slow from returning -EDEADLK and not locking
the mutex. It caused a lot of false gpu lockups on radeon with
CONFIG_DEBUG_WW_MUTEX_SLOWPATH=y because a function that shouldn't be able
to return -EDEADLK did.
Signed-off-by: NMaarten Lankhorst <maarten.lankhorst@canonical.com>
Signed-off-by: NPeter Zijlstra <peterz@infradead.org>
Cc: Alex Deucher <alexander.deucher@amd.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andrew Morton <akpm@linux-foundation.org>
Cc: Thomas Gleixner <tglx@linutronix.de>
Link: http://lkml.kernel.org/r/51F775B5.201@canonical.comSigned-off-by: NIngo Molnar <mingo@kernel.org>
上级 36f571e9
...@@ -686,7 +686,7 @@ __ww_mutex_lock(struct ww_mutex *lock, struct ww_acquire_ctx *ctx) ...@@ -686,7 +686,7 @@ __ww_mutex_lock(struct ww_mutex *lock, struct ww_acquire_ctx *ctx)
might_sleep(); might_sleep();
ret = __mutex_lock_common(&lock->base, TASK_UNINTERRUPTIBLE, ret = __mutex_lock_common(&lock->base, TASK_UNINTERRUPTIBLE,
0, &ctx->dep_map, _RET_IP_, ctx); 0, &ctx->dep_map, _RET_IP_, ctx);
if (!ret && ctx->acquired > 0) if (!ret && ctx->acquired > 1)
return ww_mutex_deadlock_injection(lock, ctx); return ww_mutex_deadlock_injection(lock, ctx);
return ret; return ret;
...@@ -702,7 +702,7 @@ __ww_mutex_lock_interruptible(struct ww_mutex *lock, struct ww_acquire_ctx *ctx) ...@@ -702,7 +702,7 @@ __ww_mutex_lock_interruptible(struct ww_mutex *lock, struct ww_acquire_ctx *ctx)
ret = __mutex_lock_common(&lock->base, TASK_INTERRUPTIBLE, ret = __mutex_lock_common(&lock->base, TASK_INTERRUPTIBLE,
0, &ctx->dep_map, _RET_IP_, ctx); 0, &ctx->dep_map, _RET_IP_, ctx);
if (!ret && ctx->acquired > 0) if (!ret && ctx->acquired > 1)
return ww_mutex_deadlock_injection(lock, ctx); return ww_mutex_deadlock_injection(lock, ctx);
return ret; return ret;
......
Markdown is supported
0% .
You are about to add 0 people to the discussion. Proceed with caution.
先完成此消息的编辑!
想要评论请 注册