From: Tilman Schmidt <tilman@imap.cc>
To: linux-kernel@vger.kernel.org
Subject: Linux v2.6.18-rc1/reiserfs INFO: possible recursive locking detected
Date: Fri, 07 Jul 2006 01:40:50 +0200 [thread overview]
Message-ID: <44AD9F82.7050006@imap.cc> (raw)
In-Reply-To: <6vtF8-99-7@gated-at.bofh.it>
[-- Attachment #1: Type: text/plain, Size: 3099 bytes --]
Found this in my syslog:
> Jul 7 00:05:53 gx110 kernel: [ 131.691049]
> Jul 7 00:05:53 gx110 kernel: [ 131.691055] =============================================
> Jul 7 00:05:53 gx110 kernel: [ 131.691074] [ INFO: possible recursive locking detected ]
> Jul 7 00:05:53 gx110 kernel: [ 131.691083] ---------------------------------------------
> Jul 7 00:05:53 gx110 kernel: [ 131.691092] udevd/3729 is trying to acquire lock:
> Jul 7 00:05:53 gx110 kernel: [ 131.691101] (&inode->i_mutex){--..}, at: [<c033c72a>] mutex_lock+0x1c/0x1f
> Jul 7 00:05:53 gx110 kernel: [ 131.691148]
> Jul 7 00:05:53 gx110 kernel: [ 131.691150] but task is already holding lock:
> Jul 7 00:05:53 gx110 kernel: [ 131.691158] (&inode->i_mutex){--..}, at: [<c033c72a>] mutex_lock+0x1c/0x1f
> Jul 7 00:05:53 gx110 kernel: [ 131.691177]
> Jul 7 00:05:53 gx110 kernel: [ 131.691179] other info that might help us debug this:
> Jul 7 00:05:53 gx110 kernel: [ 131.691189] 1 lock held by udevd/3729:
> Jul 7 00:05:53 gx110 kernel: [ 131.691195] #0: (&inode->i_mutex){--..}, at: [<c033c72a>] mutex_lock+0x1c/0x1f
> Jul 7 00:05:54 gx110 kernel: [ 131.691215]
> Jul 7 00:05:54 gx110 kernel: [ 131.691217] stack backtrace:
> Jul 7 00:05:54 gx110 kernel: [ 131.691940] [<c0103f4d>] show_trace_log_lvl+0x54/0xfd
> Jul 7 00:05:54 gx110 kernel: [ 131.691997] [<c010504d>] show_trace+0xd/0x10
> Jul 7 00:05:54 gx110 kernel: [ 131.692044] [<c0105067>] dump_stack+0x17/0x1c
> Jul 7 00:05:54 gx110 kernel: [ 131.692090] [<c012e3fa>] __lock_acquire+0x758/0x9bf
> Jul 7 00:05:54 gx110 kernel: [ 131.692336] [<c012e93e>] lock_acquire+0x5e/0x80
> Jul 7 00:05:54 gx110 kernel: [ 131.692572] [<c033c5a7>] __mutex_lock_slowpath+0xa7/0x20e
> Jul 7 00:05:54 gx110 kernel: [ 131.692796] [<c033c72a>] mutex_lock+0x1c/0x1f
> Jul 7 00:05:54 gx110 kernel: [ 131.693017] [<c01ba730>] xattr_readdir+0x50/0x456
> Jul 7 00:05:54 gx110 kernel: [ 131.694269] [<c01bb304>] reiserfs_chown_xattrs+0xdd/0x112
> Jul 7 00:05:54 gx110 kernel: [ 131.694875] [<c019dca6>] reiserfs_setattr+0x113/0x250
> Jul 7 00:05:54 gx110 kernel: [ 131.695516] [<c0174619>] notify_change+0x135/0x2c0
> Jul 7 00:05:54 gx110 kernel: [ 131.695991] [<c015b328>] chown_common+0x93/0xab
> Jul 7 00:05:54 gx110 kernel: [ 131.696388] [<c015b373>] sys_chown+0x33/0x45
> Jul 7 00:05:54 gx110 kernel: [ 131.696770] [<c0102cbd>] sysenter_past_esp+0x56/0x8d
> Jul 7 00:05:54 gx110 kernel: [ 132.094621] IA-32 Microcode Update Driver: v1.14a <tigran@veritas.com>
This is originally a SuSE 10.0 installation with a ReiserFS root
filesystem, now running a 2.6.18-rc1 kernel built on the same system
with CONFIG_REISERFS_FS=y and CONFIG_PROVE_LOCKING=y.
ts@gx110:~> uname -a
Linux gx110 2.6.18-rc1-noinitrd #1 PREEMPT Thu Jul 6 18:17:31 CEST 2006
i686 i686 i386 GNU/Linux
Regards
Tilman
--
Tilman Schmidt E-Mail: tilman@imap.cc
Bonn, Germany
It is well known that a vital ingredient of success is not knowing that
what you're attempting can't be done. [Terry Pratchett, Equal Rites]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 253 bytes --]
next prev parent reply other threads:[~2006-07-06 23:39 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 ` Tilman Schmidt [this message]
2006-07-07 6:33 ` Linux v2.6.18-rc1/reiserfs INFO: possible recursive locking detected Arjan van de Ven
2006-07-07 17:28 ` Tilman Schmidt
2006-08-12 13:21 ` Tilman Schmidt
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=44AD9F82.7050006@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