Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753309Ab3EMNjI (ORCPT ); Mon, 13 May 2013 09:39:08 -0400 Received: from mail-pa0-f54.google.com ([209.85.220.54]:46304 "EHLO mail-pa0-f54.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753041Ab3EMNjE (ORCPT ); Mon, 13 May 2013 09:39:04 -0400 Date: Mon, 13 May 2013 21:56:43 +0800 From: Zheng Liu To: Jan Kara Cc: EUNBONG SONG , "Theodore Ts'o" , Dmitry Monakhov , "linux-ext4@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "linux-xfs@vger.kernel.org" , Dave Chinner Subject: Re: Re: Re: EXT4 regression caused 4eec7 Message-ID: <20130513135643.GB12883@gmail.com> Mail-Followup-To: Jan Kara , EUNBONG SONG , Theodore Ts'o , Dmitry Monakhov , "linux-ext4@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "linux-xfs@vger.kernel.org" , Dave Chinner References: <31302271.2821368363898561.JavaMail.weblogic@epml17> <20130513131809.GG400@quack.suse.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20130513131809.GG400@quack.suse.cz> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1450 Lines: 35 On Mon, May 13, 2013 at 03:18:09PM +0200, Jan Kara wrote: > On Sun 12-05-13 13:04:59, EUNBONG SONG wrote: > > > > > > >> Since at this point it's safer to rollback the change and we can > > >> investigate more deeply how to fix it correctly for the next > > >> development cycle, this is the patch which I'm testing. > > > > >> - Ted > > > > > Hello, I've tested with your patch. But the same problem was reproduced. > > > Currently, I'm trying to git bisect. If i done git bisect, i will let you know. > > > > Hi, I've done git bisect. and panic at jbd2_journal_put_journal_head() is caused by > > ae4647fb7654676fc44a97e86eb35f9f06b99f66: "jbd2: reduce journal_head size." > > I write just code patch which revert ae4647fb7654676fc44a97e86eb35f9f06b99f66 because > > I don't know the root cause. > This is really strange. I've verified the code and all the places > modifying b_jlist or b_modified are holding bh_state lock so we should be > safe... Hi Jan, Could you please take a look at this mail [1]. I don't think we hold bh_state lock there. 1. http://www.spinics.net/lists/linux-ext4/msg38205.html Thanks, - Zheng -- 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/