summaryrefslogtreecommitdiff
path: root/Documentation/lockdep-design.txt
diff options
context:
space:
mode:
authorMing Lei <tom.leiming@gmail.com>2009-04-24 23:10:06 +0800
committerIngo Molnar <mingo@elte.hu>2009-04-26 18:21:24 +0200
commit992d7ced75322307035a0e94074eb7188612a680 (patch)
treecbbe759b02e48c379ee711ad0654965a17bcbcf2 /Documentation/lockdep-design.txt
parentb48ccb095a0c9257241261ec2bd1cbb1bdabc48b (diff)
downloadlinux-3.10-992d7ced75322307035a0e94074eb7188612a680.tar.gz
linux-3.10-992d7ced75322307035a0e94074eb7188612a680.tar.bz2
linux-3.10-992d7ced75322307035a0e94074eb7188612a680.zip
locking: Documentation: lockdep-design.txt, fix note of state bits
From source code of get_usage_char(), the previous note is not correct, so fix it. static char get_usage_char(struct lock_class *class, enum lock_usage_bit bit) { char c = '.'; if (class->usage_mask & lock_flag(bit + 2))/*LOCK_ENABLED_##STATE*/ c = '+'; if (class->usage_mask & lock_flag(bit)) {/*LOCK_USED_IN_##STATE*/ c = '-'; if (class->usage_mask & lock_flag(bit + 2)) c = '?'; } return c; } note: 1) The 'bit' parameter always is passed as LOCK_USED_IN_##STATE or LOCK_USED_IN_##STATE_READ , from get_usage_chars(). Signed-off-by: Ming Lei <tom.leiming@gmail.com> LKML-Reference: <1240585806-5744-1-git-send-email-tom.leiming@gmail.com> Signed-off-by: Ingo Molnar <mingo@elte.hu>
Diffstat (limited to 'Documentation/lockdep-design.txt')
-rw-r--r--Documentation/lockdep-design.txt6
1 files changed, 3 insertions, 3 deletions
diff --git a/Documentation/lockdep-design.txt b/Documentation/lockdep-design.txt
index 938ea22f2cc..e20d913d591 100644
--- a/Documentation/lockdep-design.txt
+++ b/Documentation/lockdep-design.txt
@@ -54,9 +54,9 @@ locking error messages, inside curlies. A contrived example:
The bit position indicates STATE, STATE-read, for each of the states listed
above, and the character displayed in each indicates:
- '.' acquired while irqs disabled
- '+' acquired in irq context
- '-' acquired with irqs enabled
+ '.' acquired while irqs disabled and not in irq context
+ '-' acquired in irq context
+ '+' acquired with irqs enabled
'?' acquired in irq context with irqs enabled.
Unused mutexes cannot be part of the cause of an error.