lockdep: fix mismatched lockdep_depth/curr_chain_hash
authorGregory Haskins <ghaskins@novell.com>
Thu, 11 Oct 2007 20:11:11 +0000 (22:11 +0200)
committerPeter Zijlstra <a.p.zijlstra@chello.nl>
Thu, 11 Oct 2007 20:11:11 +0000 (22:11 +0200)
commit3aa416b07f0adf01c090baab26fb70c35ec17623
treea2c2c2f7bd8445b138b293ba6661833f970954ee
parent94c61c0aeffe64452e742087cf803d0347ef8418
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>
kernel/lockdep.c