| To: | xfs-masters@xxxxxxxxxxx |
|---|---|
| Subject: | [xfs-masters] [Bug 7287] INFO: possible recursive locking detected: mount/3232 is trying to acquire lock |
| From: | bugme-daemon@xxxxxxxxxxxxxxxxxxx |
| Date: | Sun, 18 Nov 2007 05:41:14 -0800 (PST) |
| In-reply-to: | <bug-7287-470@xxxxxxxxxxxxxxxxxxxxxxxx/> |
| Reply-to: | xfs-masters@xxxxxxxxxxx |
| Sender: | xfs-masters-bounce@xxxxxxxxxxx |
http://bugzilla.kernel.org/show_bug.cgi?id=7287 ------- Comment #4 from evil@xxxxxxxxxx 2007-11-18 05:41 ------- Last seen in 2.6.23-rc6 (09/2007), but I've not seen this in 2.6.23-rc7, 2.6.23-rc9, 2.6.23.1 and 2.6.24-rc2. So, I guess the lock annotations for XFS made it into the kernel? If so, I'd like to see this bug closed. Thanks to all involved, Christian. # zgrep -E 'DEBUG|LOCK' /proc/config.gz | grep -v ^\# [...] CONFIG_LOCKDEP_SUPPORT=y CONFIG_DETECT_SOFTLOCKUP=y CONFIG_DEBUG_RT_MUTEXES=y CONFIG_DEBUG_PI_LIST=y CONFIG_DEBUG_SPINLOCK=y CONFIG_DEBUG_MUTEXES=y CONFIG_DEBUG_LOCK_ALLOC=y CONFIG_PROVE_LOCKING=y CONFIG_LOCKDEP=y CONFIG_DEBUG_SPINLOCK_SLEEP=y CONFIG_DEBUG_LOCKING_API_SELFTESTS=y CONFIG_DEBUG_INFO=y CONFIG_DEBUG_LIST=y CONFIG_DEBUG_STACKOVERFLOW=y -- Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | [xfs-masters] [Bug 765] xfs_force_shutdown(dm-0,0x8) called from line 1091 of file fs/xfs/xfs_trans.c, bugzilla-daemon |
|---|---|
| Next by Date: | [xfs-masters] [Bug 9400] New: nfsd gets stuck when underlying filesystem is XFS, bugme-daemon |
| Previous by Thread: | [xfs-masters] [Bug 765] xfs_force_shutdown(dm-0,0x8) called from line 1091 of file fs/xfs/xfs_trans.c, bugzilla-daemon |
| Next by Thread: | [xfs-masters] [Bug 7287] INFO: possible recursive locking detected: mount/3232 is trying to acquire lock, bugme-daemon |
| Indexes: | [Date] [Thread] [Top] [All Lists] |