From: Tilman Schmidt <tilman@imap.cc>
To: LKML <linux-kernel@vger.kernel.org>
Subject: 2.6.19-rc1: INFO: possible recursive locking detected
Date: Sun, 08 Oct 2006 21:23:50 +0200 [thread overview]
Message-ID: <45295046.8000602@imap.cc> (raw)
[-- Attachment #1: Type: text/plain, Size: 3708 bytes --]
I still get the following, apparently ReiserFS related lockdep message
shortly after boot on:
ts@gx110:~> uname -a
Linux gx110 2.6.19-rc1-noinitrd #2 PREEMPT Sat Oct 7 01:03:48 CEST 2006 i686 i686 i386 GNU/Linux
with the root filesystem being ReiserFS v3.
Oct 7 21:16:42 gx110 kernel: [ 217.130153]
Oct 7 21:16:42 gx110 kernel: [ 217.130159] =============================================
Oct 7 21:16:42 gx110 kernel: [ 217.130185] [ INFO: possible recursive locking detected ]
Oct 7 21:16:42 gx110 kernel: [ 217.130195] 2.6.19-rc1-noinitrd #2
Oct 7 21:16:42 gx110 kernel: [ 217.130202] ---------------------------------------------
Oct 7 21:16:42 gx110 kernel: [ 217.130211] kdm/3270 is trying to acquire lock:
Oct 7 21:16:42 gx110 kernel: [ 217.130221] (&inode->i_mutex){--..}, at: [<c0340702>] mutex_lock+0x1c/0x1f
Oct 7 21:16:42 gx110 kernel: [ 217.130267]
Oct 7 21:16:42 gx110 kernel: [ 217.130269] but task is already holding lock:
Oct 7 21:16:42 gx110 kernel: [ 217.130277] (&inode->i_mutex){--..}, at: [<c0340702>] mutex_lock+0x1c/0x1f
Oct 7 21:16:42 gx110 kernel: [ 217.130296]
Oct 7 21:16:42 gx110 kernel: [ 217.130298] other info that might help us debug this:
Oct 7 21:16:42 gx110 kernel: [ 217.130308] 3 locks held by kdm/3270:
Oct 7 21:16:42 gx110 kernel: [ 217.130315] #0: (&inode->i_mutex){--..}, at: [<c0340702>] mutex_lock+0x1c/0x1f
Oct 7 21:16:42 gx110 kernel: [ 217.130335] #1: (&REISERFS_I(inode)->xattr_sem){----}, at: [<c01bc851>] reiserfs_acl_chmod+0xe1/0x180
Oct 7 21:16:42 gx110 kernel: [ 217.130373] #2: (&REISERFS_SB(s)->xattr_dir_sem){----}, at: [<c01bc886>] reiserfs_acl_chmod+0x116/0x180
Oct 7 21:16:42 gx110 kernel: [ 217.130395]
Oct 7 21:16:42 gx110 kernel: [ 217.130398] stack backtrace:
Oct 7 21:16:43 gx110 kernel: [ 217.130691] [<c0103ccc>] dump_trace+0x64/0x1c9
Oct 7 21:16:43 gx110 kernel: [ 217.130745] [<c0103e43>] show_trace_log_lvl+0x12/0x25
Oct 7 21:16:43 gx110 kernel: [ 217.130790] [<c010411f>] show_trace+0xd/0x10
Oct 7 21:16:43 gx110 kernel: [ 217.130834] [<c0104139>] dump_stack+0x17/0x19
Oct 7 21:16:43 gx110 kernel: [ 217.130878] [<c012e40c>] __lock_acquire+0x74f/0x9ac
Oct 7 21:16:43 gx110 kernel: [ 217.131127] [<c012e8eb>] lock_acquire+0x4a/0x6b
Oct 7 21:16:43 gx110 kernel: [ 217.131428] [<c034057f>] __mutex_lock_slowpath+0xa7/0x20e
Oct 7 21:16:43 gx110 kernel: [ 217.131662] [<c0340702>] mutex_lock+0x1c/0x1f
Oct 7 21:16:43 gx110 kernel: [ 217.131890] [<c01bb8f2>] reiserfs_xattr_set+0xda/0x2b0
Oct 7 21:16:43 gx110 kernel: [ 217.132744] [<c01bc2f1>] reiserfs_set_acl+0x184/0x1fd
Oct 7 21:16:43 gx110 kernel: [ 217.133394] [<c01bc894>] reiserfs_acl_chmod+0x124/0x180
Oct 7 21:16:43 gx110 kernel: [ 217.134035] [<c019e41b>] reiserfs_setattr+0x20b/0x243
Oct 7 21:16:43 gx110 kernel: [ 217.134622] [<c016f23d>] notify_change+0x135/0x2bc
Oct 7 21:16:43 gx110 kernel: [ 217.135090] [<c015bcb1>] sys_fchmodat+0x9f/0xc6
Oct 7 21:16:43 gx110 kernel: [ 217.135498] [<c015bcea>] sys_chmod+0x12/0x14
Oct 7 21:16:43 gx110 kernel: [ 217.135888] [<c0102d1d>] sysenter_past_esp+0x56/0x8d
Oct 7 21:16:43 gx110 kernel: [ 217.135934] DWARF2 unwinder stuck at sysenter_past_esp+0x56/0x8d
Oct 7 21:16:43 gx110 kernel: [ 217.135950]
Oct 7 21:16:43 gx110 kernel: [ 217.135963] Leftover inexact backtrace:
Oct 7 21:16:43 gx110 kernel: [ 217.135966]
Oct 7 21:16:43 gx110 kernel: [ 217.135988] =======================
HTH
--
Tilman Schmidt E-Mail: tilman@imap.cc
Bonn, Germany
Diese Nachricht besteht zu 100% aus wiederverwerteten Bits.
Ungeöffnet mindestens haltbar bis: (siehe Rückseite)
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 253 bytes --]
reply other threads:[~2006-10-08 19:21 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=45295046.8000602@imap.cc \
--to=tilman@imap.cc \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.