From: Tilman Schmidt <tilman@imap.cc>
To: linux-kernel@vger.kernel.org
Subject: [2.6.18] INFO: possible recursive locking detected
Date: Fri, 22 Sep 2006 16:23:33 +0200 [thread overview]
Message-ID: <4513F1E5.3020700@imap.cc> (raw)
[-- Attachment #1: Type: text/plain, Size: 4766 bytes --]
I am getting this in my syslog during system startup:
Sep 22 16:11:07 gx110 kernel: [ 227.330838]
Sep 22 16:11:07 gx110 kernel: [ 227.330844] =============================================
Sep 22 16:11:07 gx110 kernel: [ 227.330867] [ INFO: possible recursive locking detected ]
Sep 22 16:11:07 gx110 kernel: [ 227.330876] ---------------------------------------------
Sep 22 16:11:07 gx110 kernel: [ 227.330885] kdm/3153 is trying to acquire lock:
Sep 22 16:11:07 gx110 kernel: [ 227.330895] (&inode->i_mutex){--..}, at: [<c03388cc>] mutex_lock+0x1c/0x1f
Sep 22 16:11:07 gx110 kernel: [ 227.330943]
Sep 22 16:11:07 gx110 kernel: [ 227.330945] but task is already holding lock:
Sep 22 16:11:07 gx110 kernel: [ 227.330953] (&inode->i_mutex){--..}, at: [<c03388cc>] mutex_lock+0x1c/0x1f
Sep 22 16:11:07 gx110 kernel: [ 227.330971]
Sep 22 16:11:07 gx110 kernel: [ 227.330973] other info that might help us debug this:
Sep 22 16:11:07 gx110 kernel: [ 227.330983] 3 locks held by kdm/3153:
Sep 22 16:11:07 gx110 kernel: [ 227.330990] #0: (&inode->i_mutex){--..}, at: [<c03388cc>] mutex_lock+0x1c/0x1f
Sep 22 16:11:07 gx110 kernel: [ 227.331010] #1: (&REISERFS_I(inode)->xattr_sem){----}, at: [<c01ba985>] reiserfs_acl_chmod+0xe1/0x180
Sep 22 16:11:07 gx110 kernel: [ 227.331041] #2: (&REISERFS_SB(s)->xattr_dir_sem){----}, at: [<c01ba9ba>] reiserfs_acl_chmod+0x116/0x180
Sep 22 16:11:07 gx110 kernel: [ 227.331064]
Sep 22 16:11:07 gx110 kernel: [ 227.331066] stack backtrace:
Sep 22 16:11:07 gx110 kernel: [ 227.331779] [<c0103fa9>] show_trace_log_lvl+0x58/0x16f
Sep 22 16:11:07 gx110 kernel: [ 227.331839] [<c0105106>] show_trace+0xd/0x10
Sep 22 16:11:07 gx110 kernel: [ 227.331886] [<c0105120>] dump_stack+0x17/0x1b
Sep 22 16:11:07 gx110 kernel: [ 227.332006] [<c012d8b1>] __lock_acquire+0x74a/0x9a7
Sep 22 16:11:07 gx110 kernel: [ 227.332257] [<c012dd90>] lock_acquire+0x4a/0x6a
Sep 22 16:11:07 gx110 kernel: [ 227.332498] [<c0338749>] __mutex_lock_slowpath+0xa7/0x20e
Sep 22 16:11:07 gx110 kernel: [ 227.332729] [<c03388cc>] mutex_lock+0x1c/0x1f
Sep 22 16:11:07 gx110 kernel: [ 227.332956] [<c01b9a26>] reiserfs_xattr_set+0xda/0x2b0
Sep 22 16:11:07 gx110 kernel: [ 227.334209] [<c01ba425>] reiserfs_set_acl+0x184/0x1fd
Sep 22 16:11:07 gx110 kernel: [ 227.334832] [<c01ba9c8>] reiserfs_acl_chmod+0x124/0x180
Sep 22 16:11:07 gx110 kernel: [ 227.335454] [<c019bfdf>] reiserfs_setattr+0x20b/0x243
Sep 22 16:11:07 gx110 kernel: [ 227.336037] [<c0173011>] notify_change+0x135/0x2bc
Sep 22 16:11:07 gx110 kernel: [ 227.336506] [<c015a2e1>] sys_fchmodat+0x9f/0xc6
Sep 22 16:11:07 gx110 kernel: [ 227.336901] [<c015a31a>] sys_chmod+0x12/0x14
Sep 22 16:11:07 gx110 kernel: [ 227.337282] [<c0102d15>] sysenter_past_esp+0x56/0x8d
Sep 22 16:11:07 gx110 kernel: [ 227.337323] DWARF2 unwinder stuck at sysenter_past_esp+0x56/0x8d
Sep 22 16:11:07 gx110 kernel: [ 227.337339] Leftover inexact backtrace:
Sep 22 16:11:07 gx110 kernel: [ 227.337354] [<c0105106>] show_trace+0xd/0x10
Sep 22 16:11:07 gx110 kernel: [ 227.337373] [<c0105120>] dump_stack+0x17/0x1b
Sep 22 16:11:07 gx110 kernel: [ 227.337393] [<c012d8b1>] __lock_acquire+0x74a/0x9a7
Sep 22 16:11:07 gx110 kernel: [ 227.337411] [<c012dd90>] lock_acquire+0x4a/0x6a
Sep 22 16:11:07 gx110 kernel: [ 227.337429] [<c0338749>] __mutex_lock_slowpath+0xa7/0x20e
Sep 22 16:11:07 gx110 kernel: [ 227.337455] [<c03388cc>] mutex_lock+0x1c/0x1f
Sep 22 16:11:07 gx110 kernel: [ 227.337474] [<c01b9a26>] reiserfs_xattr_set+0xda/0x2b0
Sep 22 16:11:07 gx110 kernel: [ 227.337492] [<c01ba425>] reiserfs_set_acl+0x184/0x1fd
Sep 22 16:11:07 gx110 kernel: [ 227.337511] [<c01ba9c8>] reiserfs_acl_chmod+0x124/0x180
Sep 22 16:11:07 gx110 kernel: [ 227.337530] [<c019bfdf>] reiserfs_setattr+0x20b/0x243
Sep 22 16:11:07 gx110 kernel: [ 227.337550] [<c0173011>] notify_change+0x135/0x2bc
Sep 22 16:11:07 gx110 kernel: [ 227.337569] [<c015a2e1>] sys_fchmodat+0x9f/0xc6
Sep 22 16:11:07 gx110 kernel: [ 227.337588] [<c015a31a>] sys_chmod+0x12/0x14
Sep 22 16:11:07 gx110 kernel: [ 227.337606] [<c0102d15>] sysenter_past_esp+0x56/0x8d
ts@gx110:~> uname -a
Linux gx110 2.6.18-noinitrd #2 PREEMPT Thu Sep 21 23:34:08 CEST 2006 i686 i686 i386 GNU/Linux
Hardware: Dell OptiPlex GX110, Intel Pentium III, 933 MHz, 512 MB RAM,
i810 chipset, 60 GB ATA DISK drive, single 30 GB ReiserFS partition
for Linux
Software: SuSE Linux 10.0 Professional with current patches plus
self-compiled kernel 2.6.18
HTH
Tilman
--
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-09-22 14:22 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=4513F1E5.3020700@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox