From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matthew Wilcox Subject: Re: [LOCKDEP] xfs: possible recursive locking detected Date: Mon, 3 Jul 2006 19:18:58 -0600 Message-ID: <20060704011858.GG1605@parisc-linux.org> References: <20060704004116.GA7612@martell.zuzino.mipt.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Ingo Molnar , linux-fsdevel@vger.kernel.org, xfs@oss.sgi.com Return-path: Received: from palinux.external.hp.com ([192.25.206.14]:25235 "EHLO palinux.external.hp.com") by vger.kernel.org with ESMTP id S1750895AbWGDBS7 (ORCPT ); Mon, 3 Jul 2006 21:18:59 -0400 To: Alexey Dobriyan Content-Disposition: inline In-Reply-To: <20060704004116.GA7612@martell.zuzino.mipt.ru> Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On Tue, Jul 04, 2006 at 04:41:16AM +0400, Alexey Dobriyan wrote: > 2.6.17-912b2539e1e062cec73e2e61448e507f7719bd08 > > While trying to remove 2 small files, 2 empty dirs and 1 empty dir on > xfs partition Probably spurious. xfs_ilock can be called on both the parent and child, which wouldn't be a deadlock. > ============================================= > [ INFO: possible recursive locking detected ] > --------------------------------------------- > rm/7596 is trying to acquire lock: > (&(&ip->i_lock)->mr_lock){----}, at: [] xfs_ilock+0x4d/0x6e > > but task is already holding lock: > (&(&ip->i_lock)->mr_lock){----}, at: [] xfs_ilock+0x4d/0x6e > > other info that might help us debug this: > 3 locks held by rm/7596: > #0: (&inode->i_mutex/1){--..}, at: [] do_rmdir+0x6c/0xc3 > #1: (&inode->i_mutex){--..}, at: [] mutex_lock+0x8/0xa > #2: (&(&ip->i_lock)->mr_lock){----}, at: [] xfs_ilock+0x4d/0x6e > > stack backtrace: > [] show_trace+0xd/0xf > [] dump_stack+0x17/0x19 > [] print_deadlock_bug+0x94/0x9e > [] check_deadlock+0x3e/0x52 > [] __lock_acquire+0x747/0x7ea > [] lock_acquire+0x5e/0x7e > [] down_write+0x19/0x33 > [] xfs_ilock+0x4d/0x6e > [] xfs_lock_dir_and_entry+0x8e/0xc8 > [] xfs_rmdir+0x1ce/0x3c9 > [] xfs_vn_rmdir+0x1c/0x44 > [] vfs_rmdir+0x5c/0x92 > [] do_rmdir+0x8c/0xc3 > [] sys_rmdir+0x10/0x12 > [] syscall_call+0x7/0xb > > - > To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html