locking/lockdep: Fix lockdep_init_map_*() confusion
authorPeter Zijlstra <peterz@infradead.org>
Fri, 17 Jun 2022 13:26:06 +0000 (15:26 +0200)
committerPeter Zijlstra <peterz@infradead.org>
Fri, 24 Jun 2022 07:48:56 +0000 (09:48 +0200)
commiteae6d58d67d9739be5f7ae2dbead1d0ef6528243
treebfb9aa2ec7b1f4d7bec5420e6a58c998375b333e
parent7e6b9db27de9f69a705c1a046d45882c768e16c3
locking/lockdep: Fix lockdep_init_map_*() confusion

Commit dfd5e3f5fe27 ("locking/lockdep: Mark local_lock_t") added yet
another lockdep_init_map_*() variant, but forgot to update all the
existing users of the most complicated version.

This could lead to a loss of lock_type and hence an incorrect report.
Given the relative rarity of both local_lock and these annotations,
this is unlikely to happen in practise, still, best fix things.

Fixes: dfd5e3f5fe27 ("locking/lockdep: Mark local_lock_t")
Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
Link: https://lkml.kernel.org/r/YqyEDtoan20K0CVD@worktop.programming.kicks-ass.net
include/linux/lockdep.h
kernel/locking/lockdep.c