login
Login
/
Register
Search
Search this site:
Forums
News
Blogs
Features
Site
Home
»
Mailing list archives
»
linux-kernel
»
2008
»
March
»
25
Re: ext3 lockdep warning in 2.6.25-rc6
view
thread
Previous message: [
thread
] [
date
] [
author
]
Next message: [
thread
] [
date
] [
author
]
[view in full thread]
From: Jan Kara
Subject:
Re: ext3 lockdep warning in 2.6.25-rc6
Date: Tuesday, March 25, 2008 - 11:29 am
> I was building a kernel using "make -j 4" inside a unionfs, mounted on top
quoted text
> of ext3. The kernel is vanilla 2.6.25-rc6 plus unionfs patches. At some > point I forced a cache flush using "echo 3 > /proc/sys/vm/drop_caches" and I > got the lockdep warning below. Note that unionfs doesn't appear to be > involved in this lockdep warning at all, so I suspect this is probably an > issue between jbd and ext3 directly. > > Let me know if I can be of more help.
Actually, I have a fix for that - attached. Can you try it? Thanks. Honza
quoted text
> [31270.749254] ======================================================= > [31270.749473] [ INFO: possible circular locking dependency detected ] > [31270.749720] 2.6.25-rc6-unionfs2 #69 > [31270.749831] ------------------------------------------------------- > [31270.749958] flush-caches.sh/9702 is trying to acquire lock: > [31270.750171] (&journal->j_list_lock){--..}, at: [<c029ef6a>] journal_try_to_free_buffers+0xa5/0x158 > [31270.751607] > [31270.751607] but task is already holding lock: > [31270.751607] (inode_lock){--..}, at: [<c02718bb>] drop_pagecache+0x45/0xd3 > [31270.751607] > [31270.751607] which lock already depends on the new lock. > [31270.751607] > [31270.751607] > [31270.751607] the existing dependency chain (in reverse order) is: > [31270.751607] > [31270.751607] -> #1 (inode_lock){--..}: > [31270.751607] [<c0231e01>] __lock_acquire+0x934/0xab8 > [31270.751607] [<c0232307>] lock_acquire+0x4e/0x6a > [31270.751607] [<c0395e33>] _spin_lock+0x23/0x32 > [31270.751607] [<c02713d2>] __mark_inode_dirty+0xbe/0x134 > [31270.751607] [<c0274b3a>] __set_page_dirty+0xdd/0xec > [31270.751607] [<c0274ba9>] mark_buffer_dirty+0x60/0x63 > [31270.751607] [<c029d2f6>] __journal_temp_unlink_buffer+0xc9/0xce > [31270.751607] [<c029d43b>] __journal_unfile_buffer+0xb/0x15 > [31270.751607] [<c029d487>] __journal_refile_buffer+0x42/0x8c > [31270.751607] [<c029fdd1>] journal_commit_transaction+0xc59/0xe64 > [31270.751607] [<c02a29f1>] kjournald+0xae/0x1b0 > [31270.751607] [<c0228833>] kthread+0x3b/0x64 > [31270.751607] [<c02039d3>] kernel_thread_helper+0x7/0x10 > [31270.751607] [<ffffffff>] 0xffffffff > [31270.751607] > [31270.751607] -> #0 (&journal->j_list_lock){--..}: > [31270.751607] [<c0231d28>] __lock_acquire+0x85b/0xab8 > [31270.751607] [<c0232307>] lock_acquire+0x4e/0x6a > [31270.751607] [<c0395e33>] _spin_lock+0x23/0x32 > [31270.751607] [<c029ef6a>] journal_try_to_free_buffers+0xa5/0x158 > [31270.751607] [<c02925fe>] ext3_releasepage+0x53/0x5c > [31270.751607] [<c023e4bd>] try_to_release_page+0x32/0x3f > [31270.751607] [<c0243f59>] __invalidate_mapping_pages+0x69/0xc6 > [31270.751607] [<c02718de>] drop_pagecache+0x68/0xd3 > [31270.751607] [<c0271972>] drop_caches_sysctl_handler+0x29/0x3f > [31270.751607] [<c0289383>] proc_sys_write+0x61/0x7e > [31270.751607] [<c02594a1>] vfs_write+0x8c/0x108 > [31270.751607] [<c0259a2b>] sys_write+0x3b/0x60 > [31270.751607] [<c0202cee>] sysenter_past_esp+0x5f/0xa5 > [31270.751607] [<ffffffff>] 0xffffffff > [31270.751607] > [31270.751607] other info that might help us debug this: > [31270.751607] > [31270.751607] 2 locks held by flush-caches.sh/9702: > [31270.751607] #0: (&type->s_umount_key#12){----}, at: [<c02718ab>] drop_pagecache+0x35/0xd3 > [31270.751607] #1: (inode_lock){--..}, at: [<c02718bb>] drop_pagecache+0x45/0xd3 > [31270.751608] > [31270.751608] stack backtrace: > [31270.751608] Pid: 9702, comm: flush-caches.sh Not tainted 2.6.25-rc6-unionfs2 #69 > [31270.751608] [<c0230687>] print_circular_bug_tail+0x5b/0x66 > [31270.751608] [<c0231d28>] __lock_acquire+0x85b/0xab8 > [31270.751608] [<c0232307>] lock_acquire+0x4e/0x6a > [31270.751608] [<c029ef6a>] ? journal_try_to_free_buffers+0xa5/0x158 > [31270.751608] [<c0395e33>] _spin_lock+0x23/0x32 > [31270.751608] [<c029ef6a>] ? journal_try_to_free_buffers+0xa5/0x158 > [31270.751608] [<c029ef6a>] journal_try_to_free_buffers+0xa5/0x158 > [31270.751608] [<c02925fe>] ext3_releasepage+0x53/0x5c > [31270.751608] [<c023e4bd>] try_to_release_page+0x32/0x3f > [31270.751608] [<c0243f59>] __invalidate_mapping_pages+0x69/0xc6 > [31270.751608] [<c02718de>] drop_pagecache+0x68/0xd3 > [31270.751608] [<c0271972>] drop_caches_sysctl_handler+0x29/0x3f > [31270.751608] [<c0289383>] proc_sys_write+0x61/0x7e > [31270.751608] [<c0289322>] ? proc_sys_write+0x0/0x7e > [31270.751608] [<c02594a1>] vfs_write+0x8c/0x108 > [31270.751608] [<c0259a2b>] sys_write+0x3b/0x60 > [31270.751608] [<c0202cee>] sysenter_past_esp+0x5f/0xa5 > [31270.751608] ======================= > -- > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to
majordomo@vger.kernel.org
> More majordomo info at
http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at
http://www.tux.org/lkml/
-- Jan Kara <jack@suse.cz> SuSE CR Labs
Previous message: [
thread
] [
date
] [
author
]
Next message: [
thread
] [
date
] [
author
]
Messages in current thread:
ext3 lockdep warning in 2.6.25-rc6
, Erez Zadok
, (Sat Mar 22, 7:37 am)
Re: ext3 lockdep warning in 2.6.25-rc6
, Peter Zijlstra
, (Sat Mar 22, 10:38 am)
Re: ext3 lockdep warning in 2.6.25-rc6
, Erez Zadok
, (Sat Mar 22, 3:34 pm)
Re: ext3 lockdep warning in 2.6.25-rc6
, Peter Zijlstra
, (Sun Mar 23, 4:06 am)
Re: ext3 lockdep warning in 2.6.25-rc6
, Jan Kara
, (Tue Mar 25, 11:29 am)
Re: ext3 lockdep warning in 2.6.25-rc6
, Erez Zadok
, (Tue Apr 1, 2:23 pm)
Re: ext3 lockdep warning in 2.6.25-rc6
, Jan Kara
, (Wed Apr 2, 1:12 am)
Re: ext3 lockdep warning in 2.6.25-rc6
, Erez Zadok
, (Wed Apr 2, 9:34 am)
Re: ext3 lockdep warning in 2.6.25-rc6
, David Chinner
, (Thu Apr 3, 8:14 pm)
Re: ext3 lockdep warning in 2.6.25-rc6
, Erez Zadok
, (Fri Apr 4, 8:37 am)
Re: ext3 lockdep warning in 2.6.25-rc6
, Jan Kara
, (Mon Apr 7, 4:47 am)
Navigation
Mailing list archives
Recent posts
Popular discussions
linux-kernel
:
David Lang
Re: [patch] MTD: fix DOC2000/2001/2001PLUS build error
Steven Rostedt
Re: [PATCH] input: Fix interrupt enable in i8042_ctr when enabling interrupt fails
Linus Torvalds
Re: [patch] epoll use a single inode ...
David Miller
Re: tg3: unable to handle null pointer dereference
Frank Seidel
Re: [RFC 13/13] Char: nozomi, cleanup read and write
git-commits-head
:
Linux Kernel Mailing List
amba: struct device - replace bus_id with dev_name(), dev_set_name()
Linux Kernel Mailing List
cpumask: make irq_set_affinity() take a const struct cpumask
Linux Kernel Mailing List
cgroups: fix probable race with put_css_set[_taskexit] and find_css_set
Linux Kernel Mailing List
[libata] Export ata_pio_queue_task() so that it can be used from sata_mv.
Linux Kernel Mailing List
[ARM] 5209/1: metronomefb: changes to use platform framebuffer
git
:
Junio C Hamano
Re: mingw, windows, crlf/lf, and git
Junio C Hamano
Re: [PATCH 1/2] Teach git-describe to display distances from tags.
Daniel Barkalow
Re: git and mtime
Linus Torvalds
Re: [PATCH] Teach 'git pull' the '--rebase' option
Alex Riesen
Re: Easy shell question: how to make a script killing all his childs when killed?
freebsd-current
:
Mark Linimon
Why the FreeBSD license will not be changing
Michael Moll
Re: Unable to boot on ECS K7S5A
FreeBSD Tinderbox
[head tinderbox] failure on ia64/ia64
Jille Timmermans
Re: svn commit: r185482 - head/sys/dev/ath/ath_rate/sample
Hayer, Sukhjinder
8_CURRENT boot problem
linux-netdev
:
Timo Teräs
ip xfrm policy semantics
Andi Kleen
Re: [ANNOUNCE]: First release of nftables
John P Poet
Realtek 8111C transmit timed out
Jeff Garzik
Re: [PATCH] fix netxen_pci_tbl[] breakage
Jesper Dangaard Brouer
[PATCH] iputils: arping fails to set correct broadcast address
Colocation donated by:
Syndicate