Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754828Ab3CKVil (ORCPT ); Mon, 11 Mar 2013 17:38:41 -0400 Received: from ud10.udmedia.de ([194.117.254.50]:55622 "EHLO mail.ud10.udmedia.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753313Ab3CKVik (ORCPT ); Mon, 11 Mar 2013 17:38:40 -0400 Date: Mon, 11 Mar 2013 22:38:37 +0100 From: Markus Trippelsdorf To: "Theodore Ts'o" , Dave Jones , linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: torrent hash failures since 3.9.0-rc1 Message-ID: <20130311213837.GA438@x4> References: <20130311171824.GA434@x4> <20130311191753.GA439@x4> <20130311194159.GB3579@redhat.com> <20130311201334.GA444@x4> <20130311203738.GB15478@thunk.org> <20130311204625.GA433@x4> <20130311211833.GC15478@thunk.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20130311211833.GC15478@thunk.org> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1718 Lines: 39 On 2013.03.11 at 17:18 -0400, Theodore Ts'o wrote: > On Mon, Mar 11, 2013 at 09:46:25PM +0100, Markus Trippelsdorf wrote: > > > BTW, I'm currently running 3.9-rc2 with some additional fixes from the > > > ext4 dev branch, and I'm not able to reproduce the problem using > > > rtorrent on my laptop. How reliably is it reproducing for you? Are > > > you seeing the problem every time you try this? > > > > Yes, it's 100% reproducible for me. If I boot a 3.8 kernel the issue > > vanishes. > > Would you be willing to try an experiment? > > Try pulling down the master branch from the ext4 git tree here: > > git://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git > > This contains all of the ext4 changes which are in 3.9-rc1, based on > top of 3.8-rc3. See if it reproduces there. If it does, then it > would tend to confirm the hypothesis that the issue was introduced by > one of the ext4 patches that we merged during the 3.9-rc1 merge > window... and then, since if you can reproduce the problem, if you > could do a git bisect to find the guilty commit, that would really > greatly appreciated. > > If you can't reproduce it from the ext4.git tree, then the problem is > probably caused by some other change that was introduced between 3.8 > and 3.9-rc1. I've started a full bisection from v3.8 to todays git tree. It will take ~13 steps. However it's already late here in Germany. I will continue the bisection tomorrow and report back. -- Markus -- 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/