Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756372AbYJGUaA (ORCPT ); Tue, 7 Oct 2008 16:30:00 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753056AbYJGU3v (ORCPT ); Tue, 7 Oct 2008 16:29:51 -0400 Received: from sandeen.net ([209.173.210.139]:19774 "EHLO sandeen.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751194AbYJGU3u (ORCPT ); Tue, 7 Oct 2008 16:29:50 -0400 Message-ID: <48EBC6B9.7000608@sandeen.net> Date: Tue, 07 Oct 2008 15:29:45 -0500 From: Eric Sandeen User-Agent: Thunderbird 2.0.0.17 (Macintosh/20080914) MIME-Version: 1.0 To: Jeremy Fitzhardinge CC: linux-ext4@vger.kernel.org, Linux Kernel Mailing List Subject: Re: ext4 deadlocks References: <48EBB9E9.4030105@goop.org> In-Reply-To: <48EBB9E9.4030105@goop.org> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 3435 Lines: 78 Jeremy Fitzhardinge wrote: > I tried giving ext4 a spin on my rawhide system, and it appears to > deadlock pretty quickly: lots of processed blocked in either ext4 or jbd2. > > From the look of the sysrq-t dumps I captured, I think beagled is > what's triggering it by doing something with EAs. I haven't had any > lockups since I killed it off. > > beagled D 0000000000000000 0 3477 1 > ffff880125809778 0000000000000082 0000000000000000 ffff88013b078150 > ffffffff8187a780 ffffffff8187a780 ffff88010f8445c0 ffff88013badc5c0 > ffff88010f844970 0000000100000001 0000000000000000 ffff88010f844970 > Call Trace: > [] ? scsi_sg_alloc+0x48/0x4a > [] __down_write_nested+0xa3/0xbd > [] __down_write+0xb/0xd > [] down_write+0x2f/0x33 > [] ext4_expand_extra_isize_ea+0x67/0x6f2 [ext4dev] At first glance it seems that we're trying a down_write on the xattr_sem here... > [] ? jbd2_journal_add_journal_head+0x113/0x1b0 [jbd2] > [] ? jbd2_journal_put_journal_head+0x1a/0x56 [jbd2] > [] ? jbd2_journal_get_write_access+0x31/0x38 [jbd2] > [] ? jbd2_journal_extend+0x1af/0x1ca [jbd2] > [] ext4_mark_inode_dirty+0x119/0x18b [ext4dev] > [] ext4_dirty_inode+0xab/0xc3 [ext4dev] > [] __mark_inode_dirty+0x38/0x194 > [] ext4_mb_new_blocks+0x700/0x70f [ext4dev] > [] ? mark_page_accessed+0x5f/0x6b > [] ? __find_get_block+0x1af/0x1c1 > [] ? __wait_on_bit+0x6f/0x7e > [] ? sync_buffer+0x0/0x44 > [] do_blk_alloc+0x9d/0xb3 [ext4dev] > [] ext4_new_meta_blocks+0x34/0x76 [ext4dev] > [] ext4_new_meta_block+0x24/0x26 [ext4dev] > [] ext4_xattr_block_set+0x50e/0x6d6 [ext4dev] > [] ext4_xattr_set_handle+0x281/0x3f0 [ext4dev] Having already downed it here? I'll look into it, not 100% sure what path gets us here (between in-inode EAs and external block EAs) but I'll see. -Eric > [] ? __jbd2_log_space_left+0x1e/0x3d [jbd2] > [] ? start_this_handle+0x4a2/0x4ca [jbd2] > [] ? jbd2_journal_start+0xa8/0xe0 [jbd2] > [] ext4_xattr_set+0xa1/0xec [ext4dev] > [] ? selinux_inode_permission+0xc1/0xca > [] ext4_xattr_user_set+0x45/0x4b [ext4dev] > [] generic_setxattr+0x7a/0x7c > [] vfs_setxattr+0x9b/0x11e > [] setxattr+0xd3/0xf2 > [] ? putname+0x35/0x3e > [] ? user_path_at+0x62/0x91 > [] ? _spin_lock+0xe/0x11 > [] sys_lsetxattr+0x60/0x89 > [] system_call_fastpath+0x16/0x1b > > > > The kernel is kernel-2.6.27-0.398.rc9.fc10.x86_64. ext4 is the /home > filesystem, mounted with noatime. I'm running a normal Fedora gnome > desktop environment. > > The sysrq-t dumps are attached. > > J > -- 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/