From: Eric Sandeen <sandeen@sandeen.net>
To: linux-kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: xfs-oss <xfs@oss.sgi.com>
Subject: [PATCH] Increase lockdep MAX_LOCK_DEPTH
Date: Thu, 30 Aug 2007 23:43:14 -0500 [thread overview]
Message-ID: <46D79C62.1010304@sandeen.net> (raw)
The xfs filesystem can exceed the current lockdep
MAX_LOCK_DEPTH, because when deleting an entire cluster of inodes,
they all get locked in xfs_ifree_cluster(). The normal cluster
size is 8192 bytes, and with the default (and minimum) inode size
of 256 bytes, that's up to 32 inodes that get locked. Throw in a
few other locks along the way, and 40 seems enough to get me through
all the tests in the xfsqa suite on 4k blocks. (block sizes
above 8K will still exceed this though, I think)
Signed-off-by: Eric Sandeen <sandeen@sandeen.net>
Index: linux-2.6.23-rc3/include/linux/sched.h
===================================================================
--- linux-2.6.23-rc3.orig/include/linux/sched.h
+++ linux-2.6.23-rc3/include/linux/sched.h
@@ -1125,7 +1125,7 @@ struct task_struct {
int softirq_context;
#endif
#ifdef CONFIG_LOCKDEP
-# define MAX_LOCK_DEPTH 30UL
+# define MAX_LOCK_DEPTH 40UL
u64 curr_chain_key;
int lockdep_depth;
struct held_lock held_locks[MAX_LOCK_DEPTH];
next reply other threads:[~2007-08-31 4:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-31 4:43 Eric Sandeen [this message]
2007-08-31 6:39 ` [PATCH] Increase lockdep MAX_LOCK_DEPTH Peter Zijlstra
2007-08-31 13:50 ` David Chinner
2007-08-31 14:33 ` Eric Sandeen
2007-08-31 14:36 ` Peter Zijlstra
2007-08-31 14:33 ` Peter Zijlstra
2007-08-31 15:05 ` David Chinner
2007-08-31 15:09 ` Peter Zijlstra
2007-08-31 15:11 ` Eric Sandeen
2007-08-31 15:19 ` David Chinner
2007-08-31 16:33 ` Josef Sipek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=46D79C62.1010304@sandeen.net \
--to=sandeen@sandeen.net \
--cc=linux-kernel@vger.kernel.org \
--cc=xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox