Gitweb:     
http://git.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=bdb9441e9c325d50b5ae17f7d3205d65b8ed2e5f
Commit:     bdb9441e9c325d50b5ae17f7d3205d65b8ed2e5f
Parent:     bfa274e2436fc7ef72ef51c878083647f1cfd429
Author:     Peter Zijlstra <[EMAIL PROTECTED]>
AuthorDate: Mon Feb 25 23:02:48 2008 +0100
Committer:  Peter Zijlstra <[EMAIL PROTECTED]>
CommitDate: Mon Feb 25 23:02:48 2008 +0100

    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 <[EMAIL PROTECTED]>
    Signed-off-by: Ingo Molnar <[EMAIL PROTECTED]>
---
 include/linux/sched.h |    2 +-
 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];
-
To unsubscribe from this list: send the line "unsubscribe git-commits-head" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to