]> bbs.cooldavid.org Git - net-next-2.6.git/commit
Documentation: kernel-locking: mutex_trylock cannot be used in interrupt context
authorStefan Richter <stefanr@s5r6.in-berlin.de>
Thu, 19 Aug 2010 21:13:43 +0000 (14:13 -0700)
committerLinus Torvalds <torvalds@linux-foundation.org>
Fri, 20 Aug 2010 16:34:56 +0000 (09:34 -0700)
commit1ee41680572971e34d90d5f584daf33195ec6dcb
treef34cc8afcba020e0b47e676b5583e5d59fc26306
parent626115cda9a31d7618cfd5ca8928811e5947d360
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 <stefanr@s5r6.in-berlin.de>
Acked-by: Rusty Russell <rusty@rustcorp.com.au>
Cc: Matthew Wilcox <matthew@wil.cx>
Cc: Randy Dunlap <rdunlap@xenotime.net>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Documentation/DocBook/kernel-locking.tmpl