Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753367AbXLXXDN (ORCPT ); Mon, 24 Dec 2007 18:03:13 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751843AbXLXXDE (ORCPT ); Mon, 24 Dec 2007 18:03:04 -0500 Received: from filer.fsl.cs.sunysb.edu ([130.245.126.2]:49121 "EHLO filer.fsl.cs.sunysb.edu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751840AbXLXXDB (ORCPT ); Mon, 24 Dec 2007 18:03:01 -0500 Date: Mon, 24 Dec 2007 18:02:24 -0500 Message-Id: <200712242302.lBON2O8s011190@agora.fsl.cs.sunysb.edu> From: Erez Zadok To: linux-kernel@vger.kernel.org, ext3-users@redhat.com Subject: lockdep warning with LTP dio test (v2.6.24-rc6-125-g5356f66) X-MailKey: Erez_Zadok Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 3381 Lines: 87 Setting: ltp-full-20071031, dio01 test on ext3 with Linus's latest tree. Kernel w/ SMP, preemption, and lockdep configured. Cheers, Erez. ======================================================= [ INFO: possible circular locking dependency detected ] 2.6.24-rc6 #83 ------------------------------------------------------- diotest1/2088 is trying to acquire lock: (&mm->mmap_sem){----}, at: [] dio_get_page+0x4e/0x15d but task is already holding lock: (jbd_handle){--..}, at: [] journal_start+0xcb/0xf8 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #1 (jbd_handle){--..}: [] __lock_acquire+0x9cc/0xb95 [] lock_acquire+0x5f/0x78 [] journal_start+0xee/0xf8 [] ext3_journal_start_sb+0x48/0x4a [] ext3_dirty_inode+0x27/0x6c [] __mark_inode_dirty+0x29/0x144 [] touch_atime+0xb7/0xbc [] generic_file_mmap+0x2d/0x42 [] mmap_region+0x1e6/0x3b4 [] do_mmap_pgoff+0x1fb/0x253 [] sys_mmap2+0x9b/0xb5 [] syscall_call+0x7/0xb [] 0xffffffff -> #0 (&mm->mmap_sem){----}: [] __lock_acquire+0x8bc/0xb95 [] lock_acquire+0x5f/0x78 [] down_read+0x3a/0x4c [] dio_get_page+0x4e/0x15d [] __blockdev_direct_IO+0x431/0xa81 [] ext3_direct_IO+0x10c/0x1a1 [] generic_file_direct_IO+0x124/0x139 [] generic_file_direct_write+0x56/0x11c [] __generic_file_aio_write_nolock+0x33d/0x489 [] generic_file_aio_write+0x58/0xb6 [] ext3_file_write+0x27/0x99 [] do_sync_write+0xc5/0x102 [] vfs_write+0x90/0x119 [] sys_write+0x3d/0x61 [] sysenter_past_esp+0x5f/0xa5 [] 0xffffffff other info that might help us debug this: 2 locks held by diotest1/2088: #0: (&sb->s_type->i_mutex_key#6){--..}, at: [] generic_file_aio_write+0x45/0xb6 #1: (jbd_handle){--..}, at: [] journal_start+0xcb/0xf8 stack backtrace: Pid: 2088, comm: diotest1 Not tainted 2.6.24-rc6 #83 [] show_trace_log_lvl+0x1a/0x2f [] show_trace+0x12/0x14 [] dump_stack+0x6c/0x72 [] print_circular_bug_tail+0x5f/0x68 [] __lock_acquire+0x8bc/0xb95 [] lock_acquire+0x5f/0x78 [] down_read+0x3a/0x4c [] dio_get_page+0x4e/0x15d [] __blockdev_direct_IO+0x431/0xa81 [] ext3_direct_IO+0x10c/0x1a1 [] generic_file_direct_IO+0x124/0x139 [] generic_file_direct_write+0x56/0x11c [] __generic_file_aio_write_nolock+0x33d/0x489 [] generic_file_aio_write+0x58/0xb6 [] ext3_file_write+0x27/0x99 [] do_sync_write+0xc5/0x102 [] vfs_write+0x90/0x119 [] sys_write+0x3d/0x61 [] sysenter_past_esp+0x5f/0xa5 ======================= -- 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/