diff options
| author | Gregory Haskins <ghaskins@novell.com> | 2007-10-11 22:11:11 +0200 |
|---|---|---|
| committer | Peter Zijlstra <a.p.zijlstra@chello.nl> | 2007-10-11 22:11:11 +0200 |
| commit | 3aa416b07f0adf01c090baab26fb70c35ec17623 (patch) | |
| tree | a2c2c2f7bd8445b138b293ba6661833f970954ee /kernel/mutex.c | |
| parent | 94c61c0aeffe64452e742087cf803d0347ef8418 (diff) | |
lockdep: fix mismatched lockdep_depth/curr_chain_hash
It is possible for the current->curr_chain_key to become inconsistent with the
current index if the chain fails to validate. The end result is that future
lock_acquire() operations may inadvertently fail to find a hit in the cache
resulting in a new node being added to the graph for every acquire.
Signed-off-by: Gregory Haskins <ghaskins@novell.com>
Signed-off-by: Peter Zijlstra <a.p.zijlstra@chello.nl>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
Diffstat (limited to 'kernel/mutex.c')
0 files changed, 0 insertions, 0 deletions