Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1762194AbZCYPS6 (ORCPT ); Wed, 25 Mar 2009 11:18:58 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1755563AbZCYPSs (ORCPT ); Wed, 25 Mar 2009 11:18:48 -0400 Received: from mail-ew0-f165.google.com ([209.85.219.165]:43811 "EHLO mail-ew0-f165.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754630AbZCYPSq convert rfc822-to-8bit (ORCPT ); Wed, 25 Mar 2009 11:18:46 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=vrtYfhcTqbRW/TTeq7vnbvCn5exikDgalSMiQ0Z0onM6hVc98M/Cktpc3Qh+GvC5Lp yblHrdTXiYGjtIdiJhhPXVIsTI5WfRz8/JxgTgKdlyVupo9UJ+A/sHlS+DBr2NcLznEa d5WKlld72YGe55jCfimq8NawrQg+xm3l32/3M= MIME-Version: 1.0 In-Reply-To: <20090325151516.GB14881@atrey.karlin.mff.cuni.cz> References: <20090310124658.GE8840@mit.edu> <20090310154745.GF23075@mit.edu> <20090325151122.GA14881@atrey.karlin.mff.cuni.cz> <20090325151516.GB14881@atrey.karlin.mff.cuni.cz> Date: Wed, 25 Mar 2009 18:18:43 +0300 Message-ID: Subject: Re: next-20090310: ext4 hangs From: Alexander Beregalov To: Jan Kara Cc: Theodore Tso , "linux-next@vger.kernel.org" , linux-ext4@vger.kernel.org, LKML Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 942 Lines: 18 2009/3/25 Jan Kara : >> > So, I think I need to try it on 2.6.29-rc7 again. >>   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 never woken >> up and because it has a handle from the transaction, every one eventually >> blocks on waiting for a transaction to finish. >>   But I don't really see how that can happen. The code is really >> straightforward and everything happens under j_list_lock... Strange. >  BTW: Is the system SMP? No, it is UP system. The bug exists even in 2.6.29, I posted it with a new topic. -- 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/