From: Jan Kara Subject: Re: next-20090310: ext4 hangs Date: Wed, 25 Mar 2009 16:22:35 +0100 Message-ID: <20090325152234.GN23439@duck.suse.cz> References: <20090310124658.GE8840@mit.edu> <20090310154745.GF23075@mit.edu> <20090325151122.GA14881@atrey.karlin.mff.cuni.cz> <20090325151516.GB14881@atrey.karlin.mff.cuni.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: Theodore Tso , "linux-next@vger.kernel.org" , linux-ext4@vger.kernel.org, LKML To: Alexander Beregalov Return-path: Content-Disposition: inline In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org List-Id: linux-ext4.vger.kernel.org On Wed 25-03-09 18:18:43, Alexander Beregalov wrote: > 2009/3/25 Jan Kara : > >> > So, I think I need to try it on 2.6.29-rc7 again. > >> =A0 I've looked into this. Obviously, what's happenning is that we= delete > >> an inode and jbd2_journal_release_jbd_inode() finds inode is just = under > >> writeout in transaction commit and thus it waits. But it gets neve= r woken > >> up and because it has a handle from the transaction, every one eve= ntually > >> blocks on waiting for a transaction to finish. > >> =A0 But I don't really see how that can happen. The code is really > >> straightforward and everything happens under j_list_lock... Strang= e. > > =A0BTW: Is the system SMP? > No, it is UP system. Even stranger. And do you have CONFIG_PREEMPT set? > The bug exists even in 2.6.29, I posted it with a new topic. OK, I've sort-of expected this. Honza --=20 Jan Kara SUSE Labs, CR