Minki/linux
1
0
Fork 1
mirror of https://github.com/torvalds/linux.git synced 2024-11-11 06:31:49 +00:00
Code Issues Packages Projects Releases Wiki Activity

locking/lockdep: Update comment

Browse Source 
A leftover comment is removed. While at it, add more explanatory
comments. Such a trivial patch!

Signed-off-by: Yuyang Du <duyuyang@gmail.com>
Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: bvanassche@acm.org
Cc: frederic@kernel.org
Cc: ming.lei@redhat.com
Cc: will.deacon@arm.com
Link: https://lkml.kernel.org/r/20190506081939.74287-12-duyuyang@gmail.com
Signed-off-by: Ingo Molnar <mingo@kernel.org>
This commit is contained in:
Yuyang Du 2019-05-06 16:19:27 +08:00 committed by Ingo Molnar
parent 0b9fc8ecfa
commit 31a490e5c5
1 changed files with 9 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
kernel/locking/lockdep.c
View File

@ -2811,10 +2811,16 @@ static int validate_chain(struct task_struct *curr,
* - is softirq-safe, if this lock is hardirq-unsafe * - is softirq-safe, if this lock is hardirq-unsafe
* *
* And check whether the new lock's dependency graph * And check whether the new lock's dependency graph
* could lead back to the previous lock. * could lead back to the previous lock:
* *
* any of these scenarios could lead to a deadlock. If * - within the current held-lock stack
* All validations * - across our accumulated lock dependency records
*
* any of these scenarios could lead to a deadlock.
*/
/*
* The simple case: does the current hold the same lock
* already?
*/ */
int ret = check_deadlock(curr, hlock, hlock->read); int ret = check_deadlock(curr, hlock, hlock->read);