From: Oliver Neukum <oliver@neukum.org>
To: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: possible circular lock dependency in reiserfs
Date: Wed, 17 Oct 2007 11:05:13 +0200 [thread overview]
Message-ID: <200710171105.13889.oliver@neukum.org> (raw)
Hi,
I got the following report in syslog:
Oct 17 10:56:35 oenone kernel: =============================================
Oct 17 10:56:35 oenone kernel: [ INFO: possible recursive locking detected ]
Oct 17 10:56:35 oenone kernel: 2.6.23-default #1
Oct 17 10:56:35 oenone kernel: ---------------------------------------------
Oct 17 10:56:35 oenone kernel: beagled/4092 is trying to acquire lock:
Oct 17 10:56:35 oenone kernel: (&inode->i_mutex){--..}, at: [<ffffffff88090081>] reiserfs_xattr_set+0xf3/0x30e [reiserfs]
Oct 17 10:56:35 oenone kernel:
Oct 17 10:56:35 oenone kernel: but task is already holding lock:
Oct 17 10:56:35 oenone kernel: (&inode->i_mutex){--..}, at: [<ffffffff802adef5>] vfs_setxattr+0x4d/0x1e0
Oct 17 10:56:35 oenone kernel:
Oct 17 10:56:35 oenone kernel: other info that might help us debug this:
Oct 17 10:56:35 oenone kernel: 3 locks held by beagled/4092:
Oct 17 10:56:35 oenone kernel: #0: (&inode->i_mutex){--..}, at: [<ffffffff802adef5>] vfs_setxattr+0x4d/0x1e0
Oct 17 10:56:35 oenone kernel: #1: (&REISERFS_I(inode)->xattr_sem){----}, at: [<ffffffff8808fb56>] reiserfs_setxattr+0x6b/0x11f [reiserfs]
Oct 17 10:56:35 oenone kernel: #2: (&REISERFS_SB(s)->xattr_dir_sem){----}, at: [<ffffffff8808fb89>] reiserfs_setxattr+0x9e/0x11f [reiserfs]
Oct 17 10:56:35 oenone kernel:
Oct 17 10:56:35 oenone kernel: stack backtrace:
Oct 17 10:56:35 oenone kernel:
Oct 17 10:56:35 oenone kernel: Call Trace:
Oct 17 10:56:35 oenone kernel: [<ffffffff80250528>] __lock_acquire+0x1b7/0xcaf
Oct 17 10:56:35 oenone kernel: [<ffffffff8025140d>] lock_acquire+0x51/0x6c
Oct 17 10:56:35 oenone kernel: [<ffffffff88090081>] :reiserfs:reiserfs_xattr_set+0xf3/0x30e
Oct 17 10:56:35 oenone kernel: [<ffffffff8024ddd1>] debug_mutex_lock_common+0x16/0x23
Oct 17 10:56:35 oenone kernel: [<ffffffff8044b824>] __mutex_lock_slowpath+0xe1/0x277
Oct 17 10:56:35 oenone kernel: [<ffffffff88090081>] :reiserfs:reiserfs_xattr_set+0xf3/0x30e
Oct 17 10:56:35 oenone kernel: [<ffffffff8024feec>] trace_hardirqs_on+0x115/0x139
Oct 17 10:56:35 oenone kernel: [<ffffffff8044d1f4>] _spin_unlock_irq+0x24/0x27
Oct 17 10:56:35 oenone kernel: [<ffffffff8044c85a>] __down_write_nested+0x34/0x9e
Oct 17 10:56:35 oenone kernel: [<ffffffff8808fbb2>] :reiserfs:reiserfs_setxattr+0xc7/0x11f
Oct 17 10:56:35 oenone kernel: [<ffffffff802adf56>] vfs_setxattr+0xae/0x1e0
Oct 17 10:56:35 oenone kernel: [<ffffffff802ae148>] setxattr+0xc0/0xdd
Oct 17 10:56:35 oenone kernel: [<ffffffff8028f376>] kmem_cache_free+0x1c4/0x1d6
Oct 17 10:56:35 oenone kernel: [<ffffffff8024feec>] trace_hardirqs_on+0x115/0x139
Oct 17 10:56:35 oenone kernel: [<ffffffff8029dae5>] do_path_lookup+0x1ae/0x22c
Oct 17 10:56:35 oenone kernel: [<ffffffff8029e340>] __user_walk_fd+0x41/0x4c
Oct 17 10:56:35 oenone kernel: [<ffffffff802ae1ae>] sys_lsetxattr+0x49/0x6a
Oct 17 10:56:35 oenone kernel: [<ffffffff8020bdfa>] tracesys+0x71/0xe1
Oct 17 10:56:35 oenone kernel: [<ffffffff8020be65>] tracesys+0xdc/0xe1
Oct 17 10:56:35 oenone kernel:
reply other threads:[~2007-10-17 9:05 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=200710171105.13889.oliver@neukum.org \
--to=oliver@neukum.org \
--cc=linux-fsdevel@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).