From: Johannes Berg <johannes@sipsolutions.net>
To: linux-fsdevel@vger.kernel.org
Subject: hfsplus lockdep report
Date: Mon, 21 Dec 2009 12:44:24 +0100 [thread overview]
Message-ID: <1261395864.3733.1.camel@johannes.local> (raw)
[-- Attachment #1: Type: text/plain, Size: 2356 bytes --]
Can't be a real recursive locking since it actually worked, so probably
just missing annotations:
[ 1676.667398] =============================================
[ 1676.667403] [ INFO: possible recursive locking detected ]
[ 1676.667407] 2.6.32-wl-46006-gdbb6e43-dirty #125
[ 1676.667410] ---------------------------------------------
[ 1676.667413] rm/5475 is trying to acquire lock:
[ 1676.667416] (&sb->s_type->i_mutex_key#11){+.+.+.}, at: [<ffffffffa03a10b2>] hfsplus_block_free+0x72/0x240 [hfsplus]
[ 1676.667430]
[ 1676.667431] but task is already holding lock:
[ 1676.667434] (&sb->s_type->i_mutex_key#11){+.+.+.}, at: [<ffffffff81117326>] vfs_unlink+0x56/0xf0
[ 1676.667446]
[ 1676.667447] other info that might help us debug this:
[ 1676.667451] 3 locks held by rm/5475:
[ 1676.667453] #0: (&sb->s_type->i_mutex_key#11/1){+.+.+.}, at: [<ffffffff811196c3>] do_unlinkat+0xa3/0x1d0
[ 1676.667466] #1: (&sb->s_type->i_mutex_key#11){+.+.+.}, at: [<ffffffff81117326>] vfs_unlink+0x56/0xf0
[ 1676.667476] #2: (&HFSPLUS_I(inode).extents_lock){+.+.+.}, at: [<ffffffffa039a1f5>] hfsplus_file_truncate+0x85/0x360 [hfsplus]
[ 1676.667488]
[ 1676.667489] stack backtrace:
[ 1676.667493] Pid: 5475, comm: rm Not tainted 2.6.32-wl-46006-gdbb6e43-dirty #125
[ 1676.667497] Call Trace:
[ 1676.667504] [<ffffffff81084f49>] print_deadlock_bug+0xd9/0xe0
[ 1676.667510] [<ffffffff81085135>] check_deadlock+0x1e5/0x1f0
[ 1676.667523] [<ffffffff810864d5>] validate_chain+0x355/0x6d0
[ 1676.667529] [<ffffffff81086c6e>] __lock_acquire+0x41e/0xa00
[ 1676.667540] [<ffffffff810872f3>] lock_acquire+0xa3/0x140
[ 1676.667555] [<ffffffff81434203>] mutex_lock_nested+0x73/0x3b0
[ 1676.667590] [<ffffffffa03a10b2>] hfsplus_block_free+0x72/0x240 [hfsplus]
[ 1676.667604] [<ffffffffa0399f6c>] hfsplus_free_extents+0x7c/0xe0 [hfsplus]
[ 1676.667612] [<ffffffffa039a4ae>] hfsplus_file_truncate+0x33e/0x360 [hfsplus]
[ 1676.667627] [<ffffffffa03989d4>] hfsplus_delete_inode+0x74/0xa0 [hfsplus]
[ 1676.667635] [<ffffffffa039c012>] hfsplus_unlink+0x172/0x1c0 [hfsplus]
[ 1676.667641] [<ffffffff81117357>] vfs_unlink+0x87/0xf0
[ 1676.667652] [<ffffffff811197b3>] do_unlinkat+0x193/0x1d0
[ 1676.667677] [<ffffffff81119962>] sys_unlinkat+0x22/0x40
[ 1676.667682] [<ffffffff8100b5fb>] system_call_fastpath+0x16/0x1b
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
reply other threads:[~2009-12-21 11:44 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=1261395864.3733.1.camel@johannes.local \
--to=johannes@sipsolutions.net \
--cc=linux-fsdevel@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;
as well as URLs for NNTP newsgroup(s).