From: Tilman Schmidt <tilman@imap.cc>
To: Arjan van de Ven <arjan@infradead.org>
Cc: mingo@elte.hu, linux-kernel@vger.kernel.org
Subject: Re: Linux v2.6.18-rc1/reiserfs INFO: possible recursive locking detected
Date: Fri, 07 Jul 2006 19:28:45 +0200 [thread overview]
Message-ID: <44AE99CD.80006@imap.cc> (raw)
In-Reply-To: <1152253999.3111.17.camel@laptopd505.fenrus.org>
[-- Attachment #1: Type: text/plain, Size: 3173 bytes --]
On 07.07.2006 08:33, Arjan van de Ven wrote:
> hmm interesting; reiserfs seems to have another locking level layer for
> the i_mutex due to the xattrs-are-a-directory thing.
>
> Can you try this patch below and see if that fixes it?
The message is still there, but the details changed a bit:
> Jul 7 19:15:48 gx110 kernel: [ 125.840979]
> Jul 7 19:15:48 gx110 kernel: [ 125.840984] =============================================
> Jul 7 19:15:48 gx110 kernel: [ 125.841003] [ INFO: possible recursive locking detected ]
> Jul 7 19:15:48 gx110 kernel: [ 125.841012] ---------------------------------------------
> Jul 7 19:15:48 gx110 kernel: [ 125.841021] kdm/3242 is trying to acquire lock:
> Jul 7 19:15:48 gx110 kernel: [ 125.841030] (&inode->i_mutex){--..}, at: [<c033c73a>] mutex_lock+0x1c/0x1f
> Jul 7 19:15:48 gx110 kernel: [ 125.841077]
> Jul 7 19:15:48 gx110 kernel: [ 125.841079] but task is already holding lock:
> Jul 7 19:15:48 gx110 kernel: [ 125.841087] (&inode->i_mutex){--..}, at: [<c033c73a>] mutex_lock+0x1c/0x1f
> Jul 7 19:15:48 gx110 kernel: [ 125.841105]
> Jul 7 19:15:48 gx110 kernel: [ 125.841107] other info that might help us debug this:
> Jul 7 19:15:48 gx110 kernel: [ 125.841117] 3 locks held by kdm/3242:
> Jul 7 19:15:48 gx110 kernel: [ 125.841123] #0: (&inode->i_mutex){--..}, at: [<c033c73a>] mutex_lock+0x1c/0x1f
> Jul 7 19:15:48 gx110 kernel: [ 125.841143] #1: (&REISERFS_I(inode)->xattr_sem){----}, at: [<c01bcb36>] reiserfs_acl_chmod+0xe0/0x182
> Jul 7 19:15:48 gx110 kernel: [ 125.841175] #2: (&REISERFS_SB(s)->xattr_dir_sem){----}, at: [<c01bcb6b>] reiserfs_acl_chmod+0x115/0x182
> Jul 7 19:15:48 gx110 kernel: [ 125.841197]
> Jul 7 19:15:48 gx110 kernel: [ 125.841199] stack backtrace:
> Jul 7 19:15:48 gx110 kernel: [ 125.841919] [<c0103f4d>] show_trace_log_lvl+0x54/0xfd
> Jul 7 19:15:48 gx110 kernel: [ 125.841975] [<c010504d>] show_trace+0xd/0x10
> Jul 7 19:15:48 gx110 kernel: [ 125.842022] [<c0105067>] dump_stack+0x17/0x1c
> Jul 7 19:15:48 gx110 kernel: [ 125.842067] [<c012e3fa>] __lock_acquire+0x758/0x9bf
> Jul 7 19:15:48 gx110 kernel: [ 125.842314] [<c012e93e>] lock_acquire+0x5e/0x80
> Jul 7 19:15:48 gx110 kernel: [ 125.842550] [<c033c5b7>] __mutex_lock_slowpath+0xa7/0x20e
> Jul 7 19:15:48 gx110 kernel: [ 125.842846] [<c033c73a>] mutex_lock+0x1c/0x1f
> Jul 7 19:15:48 gx110 kernel: [ 125.843074] [<c01bbbb8>] reiserfs_xattr_set+0xe0/0x2bc
> Jul 7 19:15:48 gx110 kernel: [ 125.844327] [<c01bc5d6>] reiserfs_set_acl+0x187/0x200
> Jul 7 19:15:48 gx110 kernel: [ 125.844957] [<c01bcb79>] reiserfs_acl_chmod+0x123/0x182
> Jul 7 19:15:48 gx110 kernel: [ 125.845581] [<c019ddab>] reiserfs_setattr+0x218/0x250
> Jul 7 19:15:48 gx110 kernel: [ 125.846168] [<c0174619>] notify_change+0x135/0x2c0
> Jul 7 19:15:48 gx110 kernel: [ 125.846637] [<c015b25a>] sys_fchmodat+0x9c/0xc3
> Jul 7 19:15:48 gx110 kernel: [ 125.847032] [<c015b293>] sys_chmod+0x12/0x14
> Jul 7 19:15:48 gx110 kernel: [ 125.847413] [<c0102cbd>] sysenter_past_esp+0x56/0x8d
Thanks,
Tilman
--
Tilman Schmidt E-Mail: tilman@imap.cc
Bonn, Germany
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 253 bytes --]
next prev parent reply other threads:[~2006-07-07 17:27 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 [this message]
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=44AE99CD.80006@imap.cc \
--to=tilman@imap.cc \
--cc=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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.