diff options
author | Stefan Richter <[email protected]> | 2010-08-19 14:13:43 -0700 |
---|---|---|
committer | Linus Torvalds <[email protected]> | 2010-08-20 09:34:56 -0700 |
commit | 1ee41680572971e34d90d5f584daf33195ec6dcb (patch) | |
tree | f34cc8afcba020e0b47e676b5583e5d59fc26306 /tools/perf/util/trace-event-scripting.c | |
parent | 626115cda9a31d7618cfd5ca8928811e5947d360 (diff) |
Documentation: kernel-locking: mutex_trylock cannot be used in interrupt context
Chapter 6 is right about mutex_trylock, but chapter 10 wasn't. This error
was introduced during semaphore-to-mutex conversion of the Unreliable
guide. :-)
If user context which performs mutex_lock() or mutex_trylock() is
preempted by interrupt context which performs mutex_trylock() on the same
mutex instance, a deadlock occurs. This is because these functions do not
disable local IRQs when they operate on mutex->wait_lock.
Signed-off-by: Stefan Richter <[email protected]>
Acked-by: Rusty Russell <[email protected]>
Cc: Matthew Wilcox <[email protected]>
Cc: Randy Dunlap <[email protected]>
Signed-off-by: Andrew Morton <[email protected]>
Signed-off-by: Linus Torvalds <[email protected]>
Diffstat (limited to 'tools/perf/util/trace-event-scripting.c')
0 files changed, 0 insertions, 0 deletions