From: Herbert Poetzl <herbert@13thfloor.at>
To: Linux Kernel ML <linux-kernel@vger.kernel.org>
Cc: shaggy@austin.ibm.com
Subject: JFS possible recursive locking
Date: Sat, 4 Nov 2006 06:03:20 +0100 [thread overview]
Message-ID: <20061104050318.GA20209@MAIL.13thfloor.at> (raw)
Stumbled about those, but had not time to investigate
(or fix) yet, just wanted to report them before they
get lost
# uname -a
Linux (none) 2.6.18.1 #1 SMP PREEMPT Sat Nov 4 05:54:06 CET 2006 i686 unknown
# mkfs.jfs -f /dev/hdc1
# mount /dev/hdc1 /test
# echo blah >/test/blah
[ 19.602318]
[ 19.602413] =============================================
[ 19.603294] [ INFO: possible recursive locking detected ]
[ 19.603817] ---------------------------------------------
[ 19.604356] sh/26 is trying to acquire lock:
[ 19.604900] (&jfs_ip->commit_mutex){--..}, at: [<782d407c>] mutex_lock+0x1c/0x20
[ 19.606262]
[ 19.606296] but task is already holding lock:
[ 19.606874] (&jfs_ip->commit_mutex){--..}, at: [<782d407c>] mutex_lock+0x1c/0x20
[ 19.607934]
[ 19.607966] other info that might help us debug this:
[ 19.608745] 2 locks held by sh/26:
[ 19.609170] #0: (&inode->i_mutex){--..}, at: [<782d407c>] mutex_lock+0x1c/0x20
[ 19.610296] #1: (&jfs_ip->commit_mutex){--..}, at: [<782d407c>] mutex_lock+0x1c/0x20
[ 19.611450]
[ 19.611479] stack backtrace:
[ 19.617847] [<78103bdc>] show_trace_log_lvl+0x17c/0x190
[ 19.619232] [<78103c02>] show_trace+0x12/0x20
[ 19.620279] [<78103d29>] dump_stack+0x19/0x20
[ 19.621311] [<78137dd2>] print_deadlock_bug+0xc2/0xd0
[ 19.625698] [<78137e43>] check_deadlock+0x63/0x80
[ 19.630094] [<781396f8>] __lock_acquire+0x348/0x9a0
[ 19.634437] [<7813a472>] lock_acquire+0x72/0x90
[ 19.638880] [<782d35d1>] __mutex_lock_slowpath+0x71/0x290
[ 19.643039] [<782d407c>] mutex_lock+0x1c/0x20
[ 19.647083] [<781ce557>] jfs_create+0xa7/0x3a0
[ 19.658696] [<78178b41>] vfs_create+0x91/0x110
[ 19.666927] [<781793a8>] open_namei+0x5f8/0x660
[ 19.675213] [<78167cec>] do_filp_open+0x2c/0x50
[ 19.682152] [<78168052>] do_sys_open+0x52/0xe0
[ 19.689115] [<781680fc>] sys_open+0x1c/0x20
[ 19.695981] [<78102c23>] syscall_call+0x7/0xb
[ 19.697148] [<6ff52af4>] 0x6ff52af4
best,
Herbert
reply other threads:[~2006-11-04 5:03 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=20061104050318.GA20209@MAIL.13thfloor.at \
--to=herbert@13thfloor.at \
--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