| From | Bart Van Assche <> | Subject | [PATCH v7 14/23] locking/lockdep: Fix a comment in add_chain_cache() | Date | Thu, 14 Feb 2019 15:00:49 -0800 |
| |
Reflect that add_chain_cache() is always called with the graph lock held.
Cc: Peter Zijlstra <peterz@infradead.org> Cc: Waiman Long <longman@redhat.com> Cc: Johannes Berg <johannes@sipsolutions.net> Signed-off-by: Bart Van Assche <bvanassche@acm.org> --- kernel/locking/lockdep.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/locking/lockdep.c b/kernel/locking/lockdep.c index 9c10fcf422f4..e983db2a2032 100644 --- a/kernel/locking/lockdep.c +++ b/kernel/locking/lockdep.c @@ -2277,7 +2277,7 @@ static inline int add_chain_cache(struct task_struct *curr, */ /* - * We might need to take the graph lock, ensure we've got IRQs + * The caller must hold the graph lock, ensure we've got IRQs * disabled to make this an IRQ-safe lock.. for recursion reasons * lockdep won't complain about its own locking errors. */ -- 2.21.0.rc0.258.g878e2cd30e-goog
|