locking: More accurate annotations for read_lock()

Browse source

On the archs using QUEUED_RWLOCKS, read_lock() is not always a recursive
read lock, actually it's only recursive if in_interrupt() is true. So
change the annotation accordingly to catch more deadlocks.

Note we used to treat read_lock() as pure recursive read locks in
lib/locking-seftest.c, and this is useful, especially for the lockdep
development selftest, so we keep this via a variable to force switching
lock annotation for read_lock().

Signed-off-by: Boqun Feng <boqun.feng@gmail.com>
Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
Link: https://lkml.kernel.org/r/20200807074238.1632519-2-boqun.feng@gmail.com

...

This commit is contained in:

Boqun Feng 2020-08-07 15:42:20 +08:00 • committed by Peter Zijlstra

parent 92b4e9f11a

commit e918188611

3 changed files with 47 additions and 1 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

23

include/linux/lockdep.h

View file

14

kernel/locking/lockdep.c

View file

11

lib/locking-selftest.c

View file