From: Tilman Schmidt <tilman@imap.cc>
To: linux-kernel@vger.kernel.org
Subject: Re: Linux v2.6.18-rc1/reiserfs INFO: possible recursive locking detected
Date: Sat, 12 Aug 2006 15:21:41 +0200 [thread overview]
Message-ID: <44DDD5E5.7010607@imap.cc> (raw)
In-Reply-To: <44AD9F82.7050006@imap.cc>
[-- Attachment #1: Type: text/plain, Size: 4275 bytes --]
FYI, the issue is still present in 2.6.18-rc4 and 2.6.18-rc3-mm2.
Here's one output from 2.6.18-rc4:
> Aug 12 13:10:43 gx110 kernel: [ 90.648896] ACPI: Getting cpuindex for acpiid 0x2
> Aug 12 13:10:45 gx110 kernel: [ 91.809779]
> Aug 12 13:10:45 gx110 kernel: [ 91.809784] =============================================
> Aug 12 13:10:45 gx110 kernel: [ 91.809807] [ INFO: possible recursive locking detected ]
> Aug 12 13:10:45 gx110 kernel: [ 91.809816] ---------------------------------------------
> Aug 12 13:10:45 gx110 kernel: [ 91.809825] udevd/3770 is trying to acquire lock:
> Aug 12 13:10:45 gx110 kernel: [ 91.809834] (&inode->i_mutex){--..}, at: [<c0338e4a>] mutex_lock+0x1c/0x1f
> Aug 12 13:10:45 gx110 kernel: [ 91.809884]
> Aug 12 13:10:45 gx110 kernel: [ 91.809887] but task is already holding lock:
> Aug 12 13:10:45 gx110 kernel: [ 91.809894] (&inode->i_mutex){--..}, at: [<c0338e4a>] mutex_lock+0x1c/0x1f
> Aug 12 13:10:45 gx110 kernel: [ 91.809912]
> Aug 12 13:10:45 gx110 kernel: [ 91.809915] other info that might help us debug this:
> Aug 12 13:10:45 gx110 kernel: [ 91.809924] 1 lock held by udevd/3770:
> Aug 12 13:10:45 gx110 kernel: [ 91.809931] #0: (&inode->i_mutex){--..}, at: [<c0338e4a>] mutex_lock+0x1c/0x1f
> Aug 12 13:10:45 gx110 kernel: [ 91.809951]
> Aug 12 13:10:45 gx110 kernel: [ 91.809953] stack backtrace:
> Aug 12 13:10:45 gx110 kernel: [ 91.810671] [<c0103fa1>] show_trace_log_lvl+0x58/0x15b
> Aug 12 13:10:45 gx110 kernel: [ 91.810729] [<c01050ea>] show_trace+0xd/0x10
> Aug 12 13:10:45 gx110 kernel: [ 91.810775] [<c0105104>] dump_stack+0x17/0x1b
> Aug 12 13:10:45 gx110 kernel: [ 91.810821] [<c012d979>] __lock_acquire+0x74a/0x9a7
> Aug 12 13:10:45 gx110 kernel: [ 91.811065] [<c012de58>] lock_acquire+0x4a/0x6a
> Aug 12 13:10:45 gx110 kernel: [ 91.811301] [<c0338cc7>] __mutex_lock_slowpath+0xa7/0x20e
> Aug 12 13:10:45 gx110 kernel: [ 91.811526] [<c0338e4a>] mutex_lock+0x1c/0x1f
> Aug 12 13:10:45 gx110 kernel: [ 91.811747] [<c01b88f3>] xattr_readdir+0x50/0x44e
> Aug 12 13:10:45 gx110 kernel: [ 91.812999] [<c01b94aa>] reiserfs_chown_xattrs+0xda/0x10f
> Aug 12 13:10:45 gx110 kernel: [ 91.813608] [<c019c1ae>] reiserfs_setattr+0x106/0x243
> Aug 12 13:10:45 gx110 kernel: [ 91.814185] [<c0172f41>] notify_change+0x135/0x2bc
> Aug 12 13:10:45 gx110 kernel: [ 91.814720] [<c015a293>] chown_common+0x93/0xab
> Aug 12 13:10:45 gx110 kernel: [ 91.815123] [<c015a2de>] sys_chown+0x33/0x45
> Aug 12 13:10:45 gx110 kernel: [ 91.815507] [<c0102d0d>] sysenter_past_esp+0x56/0x8d
> Aug 12 13:10:45 gx110 kernel: [ 91.815547] DWARF2 unwinder stuck at sysenter_past_esp+0x56/0x8d
> Aug 12 13:10:45 gx110 kernel: [ 91.815564] Leftover inexact backtrace:
> Aug 12 13:10:45 gx110 kernel: [ 91.815578] [<c01050ea>] show_trace+0xd/0x10
> Aug 12 13:10:45 gx110 kernel: [ 91.815597] [<c0105104>] dump_stack+0x17/0x1b
> Aug 12 13:10:45 gx110 kernel: [ 91.815615] [<c012d979>] __lock_acquire+0x74a/0x9a7
> Aug 12 13:10:45 gx110 kernel: [ 91.815634] [<c012de58>] lock_acquire+0x4a/0x6a
> Aug 12 13:10:45 gx110 kernel: [ 91.815651] [<c0338cc7>] __mutex_lock_slowpath+0xa7/0x20e
> Aug 12 13:10:45 gx110 kernel: [ 91.815676] [<c0338e4a>] mutex_lock+0x1c/0x1f
> Aug 12 13:10:45 gx110 kernel: [ 91.815694] [<c01b88f3>] xattr_readdir+0x50/0x44e
> Aug 12 13:10:45 gx110 kernel: [ 91.815712] [<c01b94aa>] reiserfs_chown_xattrs+0xda/0x10f
> Aug 12 13:10:45 gx110 kernel: [ 91.815731] [<c019c1ae>] reiserfs_setattr+0x106/0x243
> Aug 12 13:10:45 gx110 kernel: [ 91.815750] [<c0172f41>] notify_change+0x135/0x2bc
> Aug 12 13:10:45 gx110 kernel: [ 91.815768] [<c015a293>] chown_common+0x93/0xab
> Aug 12 13:10:45 gx110 kernel: [ 91.815789] [<c015a2de>] sys_chown+0x33/0x45
> Aug 12 13:10:45 gx110 kernel: [ 91.815807] [<c0102d0d>] sysenter_past_esp+0x56/0x8d
> Aug 12 13:10:47 gx110 kernel: [ 94.483483] IA-32 Microcode Update Driver: v1.14a <tigran@veritas.com>
Thanks
Tilman
--
Tilman Schmidt E-Mail: tilman@imap.cc
Bonn, Germany
Diese Nachricht besteht zu 100% aus wiederverwerteten Bits.
Ungeoeffnet mindestens haltbar bis: (siehe Rueckseite)
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 253 bytes --]
prev parent reply other threads:[~2006-08-12 13:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <6vtF8-99-7@gated-at.bofh.it>
2006-07-06 23:00 ` Linux v2.6.18-rc1: printk delays Tilman Schmidt
2006-07-06 23:46 ` john stultz
2006-07-07 0:18 ` Tilman Schmidt
2006-07-07 0:58 ` john stultz
2006-07-07 15:06 ` Tilman Schmidt
2006-07-17 17:02 ` Tilman Schmidt
2006-08-12 13:14 ` Tilman Schmidt
2006-07-06 23:40 ` Linux v2.6.18-rc1/reiserfs INFO: possible recursive locking detected Tilman Schmidt
2006-07-07 6:33 ` Arjan van de Ven
2006-07-07 17:28 ` Tilman Schmidt
2006-08-12 13:21 ` Tilman Schmidt [this message]
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=44DDD5E5.7010607@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.