Commit 31a490e5 authored May 06, 2019 by Yuyang Du Committed by Ingo Molnar Jun 03, 2019

locking/lockdep: Update comment



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>

parent 0b9fc8ec

kernel/locking/lockdep.c

+9 −3

Original line number	Diff line number	Diff line
		@@ -2811,10 +2811,16 @@ static int validate_chain(struct task_struct *curr,
		* - is softirq-safe, if this lock is hardirq-unsafe
		*
		* 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
		* All validations
		* - within the current held-lock stack
		* - 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);