Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753906AbXFYKuS (ORCPT ); Mon, 25 Jun 2007 06:50:18 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751786AbXFYKuH (ORCPT ); Mon, 25 Jun 2007 06:50:07 -0400 Received: from saeurebad.de ([85.214.36.134]:47312 "EHLO saeurebad.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751239AbXFYKuF (ORCPT ); Mon, 25 Jun 2007 06:50:05 -0400 Date: Mon, 25 Jun 2007 12:49:56 +0200 From: Johannes Weiner To: Linux Kernel Mailing List Cc: xfs-masters@oss.sgi.com Subject: [BUG] Lockdep warning with XFS on 2.6.22-rc6 Message-ID: <20070625104956.GA22130@saeurebad.de> Mail-Followup-To: Linux Kernel Mailing List , xfs-masters@oss.sgi.com MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="ew6BAiZeqk4r7MaW" Content-Disposition: inline User-Agent: Mutt/1.5.13 (2006-08-11) Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 3433 Lines: 97 --ew6BAiZeqk4r7MaW Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Hi, this is what just hit the ring buffer when I was surfing with elinks on a brand-new -rc6. Hannes --ew6BAiZeqk4r7MaW Content-Type: text/plain; charset=us-ascii Content-Disposition: inline; filename="lockdep-report.txt" ======================================================= [ INFO: possible circular locking dependency detected ] 2.6.22-rc6 #14 ------------------------------------------------------- elinks/4461 is trying to acquire lock: (&(&ip->i_lock)->mr_lock/1){----}, at: [] xfs_ilock+0x50/0xd0 but task is already holding lock: (&(&ip->i_lock)->mr_lock){----}, at: [] xfs_ilock+0x50/0xd0 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #1 (&(&ip->i_lock)->mr_lock){----}: [] __lock_acquire+0xe0d/0xfc0 [] lock_acquire+0x6d/0x90 [] down_write_nested+0x41/0x60 [] xfs_ilock+0x92/0xd0 [] xfs_iget_core+0x398/0x5c0 [] xfs_iget+0xbe/0x120 [] xfs_trans_iget+0xfd/0x160 [] xfs_ialloc+0xac/0x500 [] xfs_dir_ialloc+0x6c/0x2a0 [] xfs_create+0x33e/0x630 [] xfs_vn_mknod+0x19f/0x210 [] vfs_mknod+0xa2/0xf0 [] unix_bind+0x1bf/0x2e0 [] sys_bind+0x54/0x80 [] sys_socketcall+0x7d/0x260 [] sysenter_past_esp+0x5f/0x99 [] 0xffffffff -> #0 (&(&ip->i_lock)->mr_lock/1){----}: [] __lock_acquire+0xc85/0xfc0 [] lock_acquire+0x6d/0x90 [] down_read_nested+0x41/0x60 [] xfs_ilock+0x50/0xd0 [] xfs_lock_inodes+0x175/0x190 [] xfs_lock_for_rename+0x22f/0x280 [] xfs_rename+0xaf/0x8c0 [] xfs_vn_rename+0x34/0x80 [] vfs_rename+0x307/0x370 [] sys_renameat+0x1bb/0x1f0 [] sys_rename+0x28/0x30 [] sysenter_past_esp+0x5f/0x99 [] 0xffffffff other info that might help us debug this: 3 locks held by elinks/4461: #0: (&inode->i_mutex/1){--..}, at: [] lock_rename+0xe9/0xf0 #1: (&inode->i_mutex){--..}, at: [] mutex_lock+0x1c/0x20 #2: (&(&ip->i_lock)->mr_lock){----}, at: [] xfs_ilock+0x50/0xd0 stack backtrace: [] show_trace_log_lvl+0x1a/0x30 [] show_trace+0x12/0x20 [] dump_stack+0x15/0x20 [] print_circular_bug_tail+0x6c/0x80 [] __lock_acquire+0xc85/0xfc0 [] lock_acquire+0x6d/0x90 [] down_read_nested+0x41/0x60 [] xfs_ilock+0x50/0xd0 [] xfs_lock_inodes+0x175/0x190 [] xfs_lock_for_rename+0x22f/0x280 [] xfs_rename+0xaf/0x8c0 [] xfs_vn_rename+0x34/0x80 [] vfs_rename+0x307/0x370 [] sys_renameat+0x1bb/0x1f0 [] sys_rename+0x28/0x30 [] sysenter_past_esp+0x5f/0x99 ======================= --ew6BAiZeqk4r7MaW-- - 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/