Commit 040a0a37 authored by Maarten Lankhorst's avatar Maarten Lankhorst Committed by Ingo Molnar

mutex: Add support for wound/wait style locks

Wound/wait mutexes are used when other multiple lock
acquisitions of a similar type can be done in an arbitrary
order. The deadlock handling used here is called wait/wound in
the RDBMS literature: The older tasks waits until it can acquire
the contended lock. The younger tasks needs to back off and drop
all the locks it is currently holding, i.e. the younger task is

For full documentation please read Documentation/ww-mutex-design.txt.

References: default avatarMaarten Lankhorst <>
Acked-by: default avatarDaniel Vetter <>
Acked-by: default avatarRob Clark <>
Acked-by: default avatarPeter Zijlstra <>
Cc: Linus Torvalds <>
Cc: Andrew Morton <>
Cc: Thomas Gleixner <>
Link: default avatarIngo Molnar <>
parent a41b56ef
This diff is collapsed.
......@@ -3,6 +3,7 @@
#include <linux/linkage.h>
#include <linux/lockdep.h>
#include <linux/debug_locks.h>
* Mutexes - debugging helpers:
This diff is collapsed.
This diff is collapsed.
......@@ -30,6 +30,7 @@ EXPORT_SYMBOL_GPL(debug_locks);
* a locking bug is detected.
int debug_locks_silent;
* Generic 'turn off all lock debugging' function:
......@@ -44,3 +45,4 @@ int debug_locks_off(void)
return 0;
Markdown is supported
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment