From: HM <hm@glocalnet.net>
To: linux-kernel@vger.kernel.org
Subject: INFO: possible recursive locking detected using reiser and 2.6.18-rc3
Date: Wed, 02 Aug 2006 18:15:29 +0200 [thread overview]
Message-ID: <44D0CFA1.60308@glocalnet.net> (raw)
hi!
I found the following when running 2.6.18-rc3 and reiserfs.
Please cc me as I'm not on the mailing list.
/Henk
=============================================
[ INFO: possible recursive locking detected ]
---------------------------------------------
kdm/4199 is trying to acquire lock:
(&inode->i_mutex){--..}, at: [<c0297b95>] mutex_lock+0x21/0x24
but task is already holding lock:
(&inode->i_mutex){--..}, at: [<c0297b95>] mutex_lock+0x21/0x24
other info that might help us debug this:
1 lock held by kdm/4199:
#0: (&inode->i_mutex){--..}, at: [<c0297b95>] mutex_lock+0x21/0x24
stack backtrace:
[<c0103f65>] show_trace_log_lvl+0x16f/0x192
[<c010462d>] show_trace+0x12/0x14
[<c01046c9>] dump_stack+0x19/0x1b
[<c0131571>] __lock_acquire+0x8aa/0xd2a
[<c0131d63>] lock_acquire+0x6f/0x8c
[<c029798a>] __mutex_lock_slowpath+0x65/0x24f
[<c0297b95>] mutex_lock+0x21/0x24
[<f0e1092a>] xattr_readdir+0x51/0x4b1 [reiserfs]
[<f0e11452>] reiserfs_chown_xattrs+0xbd/0x10d [reiserfs]
[<f0df4b09>] reiserfs_setattr+0xf1/0x220 [reiserfs]
[<c01726aa>] notify_change+0x20a/0x280
[<c0158aba>] chown_common+0x9d/0xab
[<c0158cf3>] sys_chown+0x34/0x46
[<c0102e3d>] sysenter_past_esp+0x56/0x8d
[<b7f73410>] 0xb7f73410
[<c010462d>] show_trace+0x12/0x14
[<c01046c9>] dump_stack+0x19/0x1b
[<c0131571>] __lock_acquire+0x8aa/0xd2a
[<c0131d63>] lock_acquire+0x6f/0x8c
[<c029798a>] __mutex_lock_slowpath+0x65/0x24f
[<c0297b95>] mutex_lock+0x21/0x24
[<f0e1092a>] xattr_readdir+0x51/0x4b1 [reiserfs]
[<f0e11452>] reiserfs_chown_xattrs+0xbd/0x10d [reiserfs]
[<f0df4b09>] reiserfs_setattr+0xf1/0x220 [reiserfs]
[<c01726aa>] notify_change+0x20a/0x280
[<c0158aba>] chown_common+0x9d/0xab
[<c0158cf3>] sys_chown+0x34/0x46
[<c0102e3d>] sysenter_past_esp+0x56/0x8d
reply other threads:[~2006-08-02 16:15 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=44D0CFA1.60308@glocalnet.net \
--to=hm@glocalnet.net \
--cc=linux-kernel@vger.kernel.org \
/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