From: "Tomasz Kvarsin" <kvarsin@gmail.com>
To: linux-kernel@vger.kernel.org,
jfs-discussion@lists.sourceforge.net, shaggy@austin.ibm.com
Subject: JFS: possible recursive locking detected
Date: Tue, 9 Jan 2007 10:33:33 +0300 [thread overview]
Message-ID: <5157576d0701082333h276b99f3l7a785f6e2f250c27@mail.gmail.com> (raw)
This I got during boot with 2.6.20-rc4:
=============================================
[ INFO: possible recursive locking detected ]
2.6.20-rc4 #3
---------------------------------------------
mount/5819 is trying to acquire lock:
(&jfs_ip->commit_mutex){--..}, at: [<c03395e1>] mutex_lock+0x21/0x30
but task is already holding lock:
(&jfs_ip->commit_mutex){--..}, at: [<c03395e1>] mutex_lock+0x21/0x30
other info that might help us debug this:
2 locks held by mount/5819:
#0: (&inode->i_mutex){--..}, at: [<c03395e1>] mutex_lock+0x21/0x30
#1: (&jfs_ip->commit_mutex){--..}, at: [<c03395e1>] mutex_lock+0x21/0x30
stack backtrace:
[<c010375a>] show_trace_log_lvl+0x1a/0x30
[<c0103e62>] show_trace+0x12/0x20
[<c0103f16>] dump_stack+0x16/0x20
[<c0135e98>] __lock_acquire+0xa38/0xe00
[<c01362cf>] lock_acquire+0x6f/0x90
[<c033939a>] __mutex_lock_slowpath+0x6a/0x290
[<c03395e1>] mutex_lock+0x21/0x30
[<c01d64b0>] jfs_create+0x90/0x350
[<c0169489>] vfs_create+0xa9/0xf0
[<c016c5f7>] open_namei+0x5d7/0x630
[<c01602fc>] do_filp_open+0x2c/0x60
[<c0160377>] do_sys_open+0x47/0xe0
[<c016044c>] sys_open+0x1c/0x20
[<c0102f8e>] sysenter_past_esp+0x5f/0x99
=======================
next reply other threads:[~2007-01-09 7:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-09 7:33 Tomasz Kvarsin [this message]
2007-01-09 9:32 ` Srinivasa Ds
2007-01-09 13:56 ` Dave Kleikamp
2007-01-09 18:05 ` [PATCH] " Dave Kleikamp
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=5157576d0701082333h276b99f3l7a785f6e2f250c27@mail.gmail.com \
--to=kvarsin@gmail.com \
--cc=jfs-discussion@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=shaggy@austin.ibm.com \
/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
all inboxes | Powered by JetHome®