summaryrefslogtreecommitdiffstats
path: root/Documentation/remoteproc.txt
diff options
context:
space:
mode:
authorDavidlohr Bueso <dave@stgolabs.net>2019-10-24 20:36:34 -0700
committerIngo Molnar <mingo@kernel.org>2019-10-29 12:22:52 +0100
commita0855d24fc22d49cdc25664fb224caee16998683 (patch)
treedd119b46e9fc2214fc272b2b878799614b728257 /Documentation/remoteproc.txt
parent751459043cc87c3f0098034b15ca5252d12539ab (diff)
downloadlinux-a0855d24fc22d49cdc25664fb224caee16998683.tar.bz2
locking/mutex: Complain upon mutex API misuse in IRQ contexts
Add warning checks if mutex_trylock() or mutex_unlock() are used in IRQ contexts, under CONFIG_DEBUG_MUTEXES=y. While the mutex rules and semantics are explicitly documented, this allows to expose any abusers and robustifies the whole thing. While trylock and unlock are non-blocking, calling from IRQ context is still forbidden (lock must be within the same context as unlock). Signed-off-by: Davidlohr Bueso <dbueso@suse.de> 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: dave@stgolabs.net Link: https://lkml.kernel.org/r/20191025033634.3330-1-dave@stgolabs.net Signed-off-by: Ingo Molnar <mingo@kernel.org>
Diffstat (limited to 'Documentation/remoteproc.txt')
0 files changed, 0 insertions, 0 deletions