summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorPeter Zijlstra <a.p.zijlstra@chello.nl>2008-02-25 23:02:48 +0100
committerPeter Zijlstra <a.p.zijlstra@chello.nl>2008-02-25 23:02:48 +0100
commitbdb9441e9c325d50b5ae17f7d3205d65b8ed2e5f (patch)
tree2696d81a8c3f5bf128aab134b1f23c14d539baac
parentbfa274e2436fc7ef72ef51c878083647f1cfd429 (diff)
downloadop-kernel-dev-bdb9441e9c325d50b5ae17f7d3205d65b8ed2e5f.zip
op-kernel-dev-bdb9441e9c325d50b5ae17f7d3205d65b8ed2e5f.tar.gz
lockdep: increase MAX_LOCK_DEPTH
Some code paths exceed the current max lock depth (XFS), so increase this limit a bit. I looked at making this a dynamic allocated array, but we should not advocate insane lock depths, so stay with this as long as it works... Signed-off-by: Peter Zijlstra <a.p.zijlstra@chello.nl> Signed-off-by: Ingo Molnar <mingo@elte.hu>
-rw-r--r--include/linux/sched.h2
1 files changed, 1 insertions, 1 deletions
diff --git a/include/linux/sched.h b/include/linux/sched.h
index e217d18..e3ea124 100644
--- a/include/linux/sched.h
+++ b/include/linux/sched.h
@@ -1189,7 +1189,7 @@ struct task_struct {
int softirq_context;
#endif
#ifdef CONFIG_LOCKDEP
-# define MAX_LOCK_DEPTH 30UL
+# define MAX_LOCK_DEPTH 48UL
u64 curr_chain_key;
int lockdep_depth;
struct held_lock held_locks[MAX_LOCK_DEPTH];
OpenPOWER on IntegriCloud