From: Duncan Sands <baldrick@free.fr>
To: Ingo Molnar <mingo@elte.hu>
Cc: Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org,
Anton Altaparmakov <aia21@cantab.net>
Subject: NTFS possible circular locking deadlock (Was: Re: 2.6.17-rc6-mm1)
Date: Thu, 8 Jun 2006 12:06:41 +0200 [thread overview]
Message-ID: <200606081206.42852.baldrick@free.fr> (raw)
In-Reply-To: <20060607221142.GB6287@elte.hu>
> could you try the current lock validator combo patch from:
>
> http://redhat.com/~mingo/lockdep-patches/lockdep-combo-2.6.17-rc6-mm1.patch
>
> does that fix this for you?
With the combo patch applied:
[ 58.778002] NTFS driver 2.1.27 [Flags: R/W MODULE].
[ 58.891035]
[ 58.891039] =====================================================
[ 58.913817] [ BUG: possible circular locking deadlock detected! ]
[ 58.932102] -----------------------------------------------------
[ 58.950388] mount/2175 is trying to acquire lock:
[ 58.964491] (&ni->mrec_lock){--..}, at: [<c0292700>] mutex_lock+0x21/0x24
[ 58.985426]
[ 58.985428] but task is already holding lock:
[ 59.002985] (&rl->lock){----}, at: [<e0b274d2>] ntfs_map_runlist+0x0/0xb5 [ntfs]
[ 59.025738]
[ 59.025739] which lock already depends on the new lock,
[ 59.045892] which could lead to circular deadlocks!
[ 59.060516]
[ 59.060517] the existing dependency chain (in reverse order) is:
[ 59.083009]
[ 59.083010] -> #1 (&rl->lock){----}:
[ 59.098464] [<c012a6b0>] lock_acquire+0x58/0x74
[ 59.114489] [<e0b23c81>] ntfs_readpage+0x344/0x8f1 [ntfs]
[ 59.133137] [<c013642f>] read_cache_page+0x8e/0x137
[ 59.150229] [<e0b32cdf>] map_mft_record+0xda/0x1e5 [ntfs]
[ 59.168878] [<e0b31081>] ntfs_read_locked_inode+0x74/0xeca [ntfs]
[ 59.189605] [<e0b32527>] ntfs_read_inode_mount+0x650/0x88a [ntfs]
[ 59.210332] [<e0b3e923>] ntfs_fill_super+0x9d7/0xe86 [ntfs]
[ 59.229500] [<c0156fee>] get_sb_bdev+0xed/0x14e
[ 59.245526] [<e0b3b49e>] ntfs_get_sb+0x10/0x12 [ntfs]
[ 59.263136] [<c01564b4>] vfs_kern_mount+0x30/0x9e
[ 59.279682] [<c015655b>] do_kern_mount+0x29/0x3d
[ 59.295968] [<c0169cfe>] do_mount+0x6c4/0x702
[ 59.311475] [<c0169d9b>] sys_mount+0x5f/0x96
[ 59.326720] [<c0293dbd>] sysenter_past_esp+0x56/0x8d
[ 59.344045]
[ 59.344046] -> #0 (&ni->mrec_lock){--..}:
[ 59.360797] [<c012a6b0>] lock_acquire+0x58/0x74
[ 59.376822] [<c0292569>] __mutex_lock_slowpath+0xa7/0x21d
[ 59.395447] [<c0292700>] mutex_lock+0x21/0x24
[ 59.411785] [<e0b32c1e>] map_mft_record+0x19/0x1e5 [ntfs]
[ 59.430433] [<e0b26cc7>] ntfs_map_runlist_nolock+0x48/0x443 [ntfs]
[ 59.451420] [<e0b27559>] ntfs_map_runlist+0x87/0xb5 [ntfs]
[ 59.470329] [<e0b23da7>] ntfs_readpage+0x46a/0x8f1 [ntfs]
[ 59.488977] [<c013642f>] read_cache_page+0x8e/0x137
[ 59.506042] [<e0b3c918>] load_system_files+0x1da/0x180e [ntfs]
[ 59.525989] [<e0b3e9c8>] ntfs_fill_super+0xa7c/0xe86 [ntfs]
[ 59.545160] [<c0156fee>] get_sb_bdev+0xed/0x14e
[ 59.561186] [<e0b3b49e>] ntfs_get_sb+0x10/0x12 [ntfs]
[ 59.578795] [<c01564b4>] vfs_kern_mount+0x30/0x9e
[ 59.595341] [<c015655b>] do_kern_mount+0x29/0x3d
[ 59.611625] [<c0169cfe>] do_mount+0x6c4/0x702
[ 59.627133] [<c0169d9b>] sys_mount+0x5f/0x96
[ 59.642379] [<c0293dbd>] sysenter_past_esp+0x56/0x8d
[ 59.659703]
[ 59.659704] other info that might help us debug this:
[ 59.659706]
[ 59.683833] 2 locks held by mount/2175:
[ 59.695340] #0: (&s->s_umount#17){--..}, at: [<c0156bd7>] sget+0x173/0x384
[ 59.716923] #1: (&rl->lock){----}, at: [<e0b274d2>] ntfs_map_runlist+0x0/0xb5 [ntfs]
[ 59.741054]
[ 59.741056] stack backtrace:
[ 59.754432] [<c0102fef>] show_trace_log_lvl+0x54/0xfd
[ 59.769927] [<c0104078>] show_trace+0xd/0x10
[ 59.783096] [<c0104092>] dump_stack+0x17/0x19
[ 59.796525] [<c012892b>] print_circular_bug_tail+0x59/0x64
[ 59.813451] [<c012a1b2>] __lock_acquire+0x7c6/0x97e
[ 59.828548] [<c012a6b0>] lock_acquire+0x58/0x74
[ 59.842622] [<c0292569>] __mutex_lock_slowpath+0xa7/0x21d
[ 59.859261] [<c0292700>] mutex_lock+0x21/0x24
[ 59.872792] [<e0b32c1e>] map_mft_record+0x19/0x1e5 [ntfs]
[ 59.889363] [<e0b26cc7>] ntfs_map_runlist_nolock+0x48/0x443 [ntfs]
[ 59.908250] [<e0b27559>] ntfs_map_runlist+0x87/0xb5 [ntfs]
[ 59.925056] [<e0b23da7>] ntfs_readpage+0x46a/0x8f1 [ntfs]
[ 59.941599] [<c013642f>] read_cache_page+0x8e/0x137
[ 59.956736] [<e0b3c918>] load_system_files+0x1da/0x180e [ntfs]
[ 59.974601] [<e0b3e9c8>] ntfs_fill_super+0xa7c/0xe86 [ntfs]
[ 59.991693] [<c0156fee>] get_sb_bdev+0xed/0x14e
[ 60.005897] [<e0b3b49e>] ntfs_get_sb+0x10/0x12 [ntfs]
[ 60.021427] [<c01564b4>] vfs_kern_mount+0x30/0x9e
[ 60.036128] [<c015655b>] do_kern_mount+0x29/0x3d
[ 60.050569] [<c0169cfe>] do_mount+0x6c4/0x702
[ 60.064291] [<c0169d9b>] sys_mount+0x5f/0x96
[ 60.077732] [<c0293dbd>] sysenter_past_esp+0x56/0x8d
[ 60.144343] NTFS volume version 3.1.
[ 60.155117] NTFS-fs warning (device hda1): load_system_files(): Unsupported volume flags 0x4000 encountered.
[ 60.184594] NTFS-fs error (device hda1): load_system_files(): Volume has unsupported flags set. Mounting read-only. Run chkdsk and mount in Windows.
next prev parent reply other threads:[~2006-06-08 10:06 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-07 17:47 2.6.17-rc6-mm1 Andrew Morton
2006-06-07 21:23 ` 2.6.17-rc6-mm1 J.A. Magallón
2006-06-07 22:07 ` 2.6.17-rc6-mm1 Ingo Molnar
2006-06-07 22:36 ` 2.6.17-rc6-mm1 J.A. Magallón
2006-06-07 23:54 ` 2.6.17-rc6-mm1 Stefan Richter
2006-06-08 0:31 ` 2.6.17-rc6-mm1 Chris Wright
2006-06-08 6:30 ` 2.6.17-rc6-mm1 Stefan Richter
2006-06-08 7:26 ` 2.6.17-rc6-mm1 Ingo Molnar
2006-06-07 21:54 ` 2.6.17-rc6-mm1 Rafael J. Wysocki
2006-06-07 22:11 ` 2.6.17-rc6-mm1 Ingo Molnar
2006-06-08 3:19 ` 2.6.17-rc6-mm1 Valdis.Kletnieks
2006-06-08 15:13 ` lockdep wierdness - was 2.6.17-rc6-mm1 Valdis.Kletnieks
2006-06-08 10:06 ` Duncan Sands [this message]
2006-06-12 14:35 ` NTFS possible circular locking deadlock (Was: Re: 2.6.17-rc6-mm1) Ingo Molnar
2006-06-08 12:54 ` 2.6.17-rc6-mm1 Rafael J. Wysocki
2006-06-07 22:31 ` 2.6.17-rc6-mm1 J.A. Magallón
2006-06-07 22:40 ` 2.6.17-rc6-mm1 Andrew Morton
2006-06-07 23:23 ` [PATCH] ignore smp_locks section warnings from init/exit code Randy.Dunlap
2006-06-08 0:04 ` Randy.Dunlap
2006-06-08 2:11 ` Jeff Dike
2006-06-08 2:32 ` Randy.Dunlap
2006-06-08 4:21 ` Jeff Dike
2006-06-08 4:29 ` Randy.Dunlap
2006-06-08 15:44 ` Randy.Dunlap
2006-06-08 18:35 ` Sam Ravnborg
2006-06-11 23:25 ` Jeff Dike
2006-06-12 0:17 ` Randy.Dunlap
2006-06-12 2:29 ` Jeff Dike
2006-06-12 2:52 ` Randy.Dunlap
2006-06-08 2:25 ` 2.6.17-rc6-mm1 Andi Kleen
2006-06-08 2:46 ` 2.6.17-rc6-mm1 Randy.Dunlap
2006-06-08 5:43 ` 2.6.17-rc6-mm1 Andi Kleen
2006-06-08 6:46 ` 2.6.17-rc6-mm1 Gerd Hoffmann
2006-06-07 23:14 ` 2.6.17-rc6-mm1 Martin Bligh
2006-06-07 23:55 ` 2.6.17-rc6-mm1 Andrew Morton
2006-06-08 1:09 ` 2.6.17-rc6-mm1 Grant Coady
2006-06-08 5:00 ` 2.6.17-rc6-mm1 Dave Jones
2006-06-20 17:42 ` 2.6.17-rc6-mm1 Arjan van de Ven
2006-06-20 20:24 ` 2.6.17-rc6-mm1 Andrew Morton
2006-06-20 20:38 ` 2.6.17-rc6-mm1 Arjan van de Ven
2006-06-21 6:23 ` 2.6.17-rc6-mm1 Dave Jones
2006-06-21 8:15 ` 2.6.17-rc6-mm1 Arjan van de Ven
2006-06-21 18:42 ` 2.6.17-rc6-mm1 Dave Jones
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=200606081206.42852.baldrick@free.fr \
--to=baldrick@free.fr \
--cc=aia21@cantab.net \
--cc=akpm@osdl.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox