- 28 Jul, 2008 1 commit
-
-
Randy Dunlap authored
Fix @key parameter to mutex_init() and one of its callers. Warning(linux-2.6.26-git11//drivers/base/class.c:210): No description found for parameter 'key' Signed-off-by:
Randy Dunlap <randy.dunlap@oracle.com> Acked-by:
Greg Kroah-Hartman <gregkh@suse.de> Signed-off-by:
Ingo Molnar <mingo@elte.hu>
-
- 10 Jun, 2008 1 commit
-
-
Oleg Nesterov authored
Change __mutex_lock_common() to use signal_pending_state() for the sake of the code re-use. This adds 7 bytes to kernel/mutex.o, but afaics only because gcc isn't smart enough. (btw, uninlining of __mutex_lock_common() shrinks .text from 2722 to 1542, perhaps it is worth doing). Signed-off-by:
Oleg Nesterov <oleg@tv-sign.ru> Signed-off-by:
-
- 08 Feb, 2008 1 commit
-
-
Harvey Harrison authored
[akpm@linux-foundation.org: coding-style fixes] Signed-off-by:
Harvey Harrison <harvey.harrison@gmail.com> Acked-by:
Andrew Morton <akpm@linux-foundation.org> Signed-off-by:
Linus Torvalds <torvalds@linux-foundation.org>
-
- 06 Dec, 2007 1 commit
-
-
Liam R. Howlett authored
Similar to mutex_lock_interruptible, it can be interrupted by a fatal signal only. Signed-off-by:
Liam R. Howlett <howlett@gmail.com> Acked-by:
Matthew Wilcox <willy@linux.intel.com>
-
- 11 Oct, 2007 1 commit
-
-
Peter Zijlstra authored
The fancy mutex_lock fastpath has too many indirections to track the caller hence all contentions are perceived to come from mutex_lock(). Avoid this by explicitly not using the fastpath code (it was disabled already anyway). Signed-off-by:
Peter Zijlstra <a.p.zijlstra@chello.nl> Signed-off-by:
-
- 19 Jul, 2007 2 commits
-
-
Peter Zijlstra authored
__acquire | lock _____ | \ | __contended | | | wait | _______/ |/ | __acquired | __release | unlock We measure acquisition and contention bouncing. This is done by recording a cpu stamp in each lock instance. Contention bouncing requires the cpu stamp to be set on acquisition. Hence we move __acquired into the generic path. __acquired is then used to measure acquisition bouncing by comparing the current cpu with the old stamp before replacing it. __contended is used to measure contention bouncing (only useful for preemptable locks) [akpm@linux-foundation.org: cleanups] Signed-off-by: -
Peter Zijlstra authored
Call the new lockstat tracking functions from the various lock primitives. Signed-off-by:
Jason Baron <jbaron@redhat.com> Signed-off-by:
-
- 09 May, 2007 1 commit
-
-
Roman Zippel authored
Recently a few direct accesses to the thread_info in the task structure snuck back, so this wraps them with the appropriate wrapper. Signed-off-by:
Roman Zippel <zippel@linux-m68k.org> Signed-off-by:
-
- 08 Dec, 2006 1 commit
-
-
NeilBrown authored
md_open takes ->reconfig_mutex which causes lockdep to complain. This (normally) doesn't have deadlock potential as the possible conflict is with a reconfig_mutex in a different device. I say "normally" because if a loop were created in the array->member hierarchy a deadlock could happen. However that causes bigger problems than a deadlock and should be fixed independently. So we flag the lock in md_open as a nested lock. This requires defining mutex_lock_interruptible_nested. Cc: Ingo Molnar <mingo@elte.hu> Acked-by:
Neil Brown <neilb@suse.de> Signed-off-by:
Andrew Morton <akpm@osdl.org> Signed-off-by:
Linus Torvalds <torvalds@osdl.org>
-
- 03 Jul, 2006 4 commits
-
-
Ingo Molnar authored
Use the lock validator framework to prove mutex locking correctness. Signed-off-by:
Arjan van de Ven <arjan@linux.intel.com> Signed-off-by:
-
Ingo Molnar authored
Work around weird section nesting build bug causing smp-alternatives failures under certain circumstances. Signed-off-by:
-
Ingo Molnar authored
Generic lock debugging: - generalized lock debugging framework. For example, a bug in one lock subsystem turns off debugging in all lock subsystems. - got rid of the caller address passing (__IP__/__IP_DECL__/etc.) from the mutex/rtmutex debugging code: it caused way too much prototype hackery, and lockdep will give the same information anyway. - ability to do silent tests - check lock freeing in vfree too. - more finegrained debugging options, to allow distributions to turn off more expensive debugging features. There's no separate 'held mutexes' list anymore - but there's a 'held locks' stack within lockdep, which unifies deadlock detection across all lock classes. (this is independent of the lockdep validation stuff - lockdep first checks whether we are holding a lock already) Here are the current debugging options: CONFIG_DEBUG_MUTEXES=y CONFIG_DEBUG_LOCK_ALLOC=y which do: config DEBUG_MUTEXES bool "Mutex debugging, basic checks" config DEBUG_LOCK_ALLOC bool "Detect incorrect freeing of live mutexes" Signed-off-by: -
Ingo Molnar authored
Rename DEBUG_WARN_ON() to the less generic DEBUG_LOCKS_WARN_ON() name, so that it's clear that this is a lock-debugging internal mechanism. Signed-off-by:
-
- 26 Jun, 2006 1 commit
-
-
Ingo Molnar authored
It seems ppc64 wants to lock mutexes in early bootup code, with interrupts disabled, and they expect interrupts to stay disabled, else they crash. Work around this bug by making mutex debugging variants save/restore irq flags. Signed-off-by:
-
- 10 Jan, 2006 3 commits
-
-
Ingo Molnar authored
Signed-off-by:
-
Ingo Molnar authored
Mark mutex_lock() and mutex_lock_interruptible() as might_sleep() functions. Signed-off-by:
-
Ingo Molnar authored
Call the mutex slowpath more conservatively - e.g. FRAME_POINTERS can change the calling convention, in which case a direct branch to the slowpath becomes illegal. Bug found by Hugh Dickins. Signed-off-by:
-
- 09 Jan, 2006 1 commit
-
-
Ingo Molnar authored
mutex implementation, core files: just the basic subsystem, no users of it. Signed-off-by:
Arjan van de Ven <arjan@infradead.org>
-
