The patch titled
Doc/lockdep-design: explain display of {state-bits}
has been removed from the -mm tree. Its filename is
doc-lockdep-design-explain-display-of-state-bits.patch
This patch was dropped because it was merged into mainline or a subsystem tree
------------------------------------------------------
Subject: Doc/lockdep-design: explain display of {state-bits}
From: Jim Cromie <jim.cromie@xxxxxxxxx>
Signed-off-by: Jim Cromie <jim.cromie@xxxxxxxxx>
Cc: Ingo Molnar <mingo@xxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxx>
---
Documentation/lockdep-design.txt | 22 ++++++++++++++++++++++
1 file changed, 22 insertions(+)
diff -puN Documentation/lockdep-design.txt~doc-lockdep-design-explain-display-of-state-bits Documentation/lockdep-design.txt
--- a/Documentation/lockdep-design.txt~doc-lockdep-design-explain-display-of-state-bits
+++ a/Documentation/lockdep-design.txt
@@ -36,6 +36,28 @@ The validator tracks lock-class usage hi
- 'ever used' [ == !unused ]
+When locking rules are violated, these 4 state bits are presented in the
+locking error messages, inside curlies. A contrived example:
+
+ modprobe/2287 is trying to acquire lock:
+ (&sio_locks[i].lock){--..}, at: [<c02867fd>] mutex_lock+0x21/0x24
+
+ but task is already holding lock:
+ (&sio_locks[i].lock){--..}, at: [<c02867fd>] mutex_lock+0x21/0x24
+
+
+The bit position indicates hardirq, softirq, hardirq-read,
+softirq-read respectively, and the character displayed in each
+indicates:
+
+ '.' acquired while irqs enabled
+ '+' acquired in irq context
+ '-' acquired in process context with irqs disabled
+ '?' read-acquired both with irqs enabled and in irq context
+
+Unused mutexes cannot be part of the cause of an error.
+
+
Single-lock state rules:
------------------------
_
Patches currently in -mm which might be from jim.cromie@xxxxxxxxx are
origin.patch
-
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
