linux-ext4 - Re: A warning from 3.6+ with bigalloc and delalloc when running xfstest

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-next>] [day] [month] [year] [list]

Message-ID: <20121009062931.GA29314@gmail.com>
Date:	Tue, 9 Oct 2012 14:29:31 +0800
From:	Zheng Liu <gnehzuil.liu@...il.com>
To:	Theodore Ts'o <tytso@....edu>
Cc:	linux-ext4@...r.kernel.org
Subject: Re: A warning from 3.6+ with bigalloc and delalloc when running
 xfstest

On Tue, Oct 09, 2012 at 01:48:20AM -0400, Theodore Ts'o wrote:
> On Mon, Oct 08, 2012 at 10:59:34PM +0800, Zheng Liu wrote:
> > 
> > This warning is printed when test case #127 and #225 are being run
> > with bigalloc and delalloc.  You could use the following commands to
> > reproduce it using xfstest.
> 
> Ah, I see I misunderstood you; I thought you had said that the tests
> had failed, I didn't realize what what you had meant was that they
> were trigging a WARN_ON.
> 
> I believe this warning is related to the general class of bugs
> surrounding bigalloc and delalloc, once we get the extent status tree
> in mainline, I'm hoping we will be able to use it to significantly
> improve how we handle bigalloc's delalloc handling.
> 
> Here are the results I have from running my tests, as well as the
> results from right after the previous merge window for comparison....

Sorry for my bad expression. :-(

OK, I see.  Thanks for the result.  It is very useful for me to
understand whether or not my patches break something up.

Regards,
Zheng
--
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