From mboxrd@z Thu Jan 1 00:00:00 1970
From: bugzilla-daemon@bugzilla.kernel.org
Subject: [Bug 13598] New: FIEMAP related circular locking dependency detected
Date: Mon, 22 Jun 2009 09:01:56 GMT
Message-ID:
Mime-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
To: linux-ext4@vger.kernel.org
Return-path:
Received: from demeter.kernel.org ([140.211.167.39]:54615 "EHLO
demeter.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
with ESMTP id S1754947AbZFVJBx (ORCPT
); Mon, 22 Jun 2009 05:01:53 -0400
Received: from demeter.kernel.org (localhost.localdomain [127.0.0.1])
by demeter.kernel.org (8.14.2/8.14.2) with ESMTP id n5M91uKB023455
for ; Mon, 22 Jun 2009 09:01:56 GMT
Sender: linux-ext4-owner@vger.kernel.org
List-ID:
http://bugzilla.kernel.org/show_bug.cgi?id=13598
Summary: FIEMAP related circular locking dependency detected
Product: File System
Version: 2.5
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: ext4
AssignedTo: fs_ext4@kernel-bugs.osdl.org
ReportedBy: aneesh.kumar@linux.vnet.ibm.com
Regression: No
Have a bugzilla entry for tracking the problem.
reported here http://article.gmane.org/gmane.comp.file-systems.ext4/13076
[ INFO: possible circular locking dependency detected ]
2.6.30-rc4-autokern1 #1
-------------------------------------------------------
a.out/5595 is trying to acquire lock:
(&mm->mmap_sem){++++++}, at: [] might_fault+0x35/0x72
but task is already holding lock:
(&ei->i_data_sem){++++..}, at: [] ext4_fiemap+0x139/0x191
which lock already depends on the new lock.
the existing dependency chain (in reverse order) is:
-> #1 (&ei->i_data_sem){++++..}:
[] validate_chain+0x89b/0xba1
[] __lock_acquire+0x6a4/0x73c
[] lock_acquire+0xa8/0xc8
[] down_read+0x1e/0x5b
[] ext4_get_blocks_wrap+0x28/0x27e
[] ext4_get_block+0x94/0xc9
[] do_mpage_readpage+0x24b/0x5e0
[] mpage_readpages+0x74/0xa8
[] ext4_readpages+0x14/0x16
[] __do_page_cache_readahead+0x14f/0x1b8
[] do_page_cache_readahead+0x42/0x53
[] filemap_fault+0x194/0x3ad
[] __do_fault+0x3b/0x35c
[] handle_mm_fault+0x36d/0x7a9
[] do_page_fault+0x28d/0x2f1
[] error_code+0x72/0x78
[] 0xffffffff
-> #0 (&mm->mmap_sem){++++++}:
[] validate_chain+0x5cf/0xba1
[] __lock_acquire+0x6a4/0x73c
[] lock_acquire+0xa8/0xc8
[] might_fault+0x52/0x72
[] copy_to_user+0x28/0x3f
[] fiemap_fill_next_extent+0x9e/0xc9
[] ext4_ext_fiemap_cb+0x1a7/0x1c1
[] ext4_ext_walk_space+0x194/0x207
[] ext4_fiemap+0x17c/0x191
[] do_vfs_ioctl+0x32a/0x4a6
[] sys_ioctl+0x40/0x5a
[] sysenter_do_call+0x12/0x32
[] 0xffffffff
other info that might help us debug this:
1 lock held by a.out/5595:
#0: (&ei->i_data_sem){++++..}, at: [] ext4_fiemap+0x139/0x191
stack backtrace:
Pid: 5595, comm: a.out Not tainted 2.6.30-rc4-autokern1 #1
Call Trace:
[] print_circular_bug_tail+0xab/0xb6
[] validate_chain+0x5cf/0xba1
[] __lock_acquire+0x6a4/0x73c
[] lock_acquire+0xa8/0xc8
[] ? might_fault+0x35/0x72
[] might_fault+0x52/0x72
[] ? might_fault+0x35/0x72
[] copy_to_user+0x28/0x3f
[] fiemap_fill_next_extent+0x9e/0xc9
[] ext4_ext_fiemap_cb+0x1a7/0x1c1
[] ext4_ext_walk_space+0x194/0x207
[] ext4_fiemap+0x17c/0x191
[] ? ext4_ext_fiemap_cb+0x0/0x1c1
[] do_vfs_ioctl+0x32a/0x4a6
[] sys_ioctl+0x40/0x5a
[] sysenter_do_call+0x12/0x32
--
--
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.