linux-ext4 - Re: ext4 blocks up

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20120702164548.GD18074@thunk.org>
Date:	Mon, 2 Jul 2012 12:45:48 -0400
From:	Theodore Ts'o <tytso@....edu>
To:	Artem Bityutskiy <dedekind1@...il.com>,
	Ext4 Mailing List <linux-ext4@...r.kernel.org>,
	Linux FS Maling List <linux-fsdevel@...r.kernel.org>,
	Linux Kernel Maling List <linux-kernel@...r.kernel.org>
Subject: Re: ext4 blocks up

On Mon, Jul 02, 2012 at 11:14:42AM -0400, Theodore Ts'o wrote:
> On Mon, Jul 02, 2012 at 05:54:22PM +0300, Artem Bityutskiy wrote:
> > On Mon, 2012-07-02 at 10:44 -0400, Theodore Ts'o wrote:
> > > Can you tell me *which* xfstest this was blocking on?
> > 
> > Test 068 which runs fsstress.
> 
> Hmmm, I had just started an xfstests -g auto run using standard ext4
> defaults with 3.5-rc2, and I'm not noting any problems.  And I've
> gotten past test 68 w/o any problems.

I just tried again with 3.5-rc5, and I was able to reproduce your
failure by using "check 68 68 68 68 68" (it failed after the 2nd time
it ran the fsstress test.  What's interesting is that there have been
no changes in fs/ext4 or fs/jbd2 since 3.5-rc2.  So this may have been
caused by a writeback related change; I'm starting a bisect now.

       	      	      	      	   	     - Ted
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html