linux-ext4 - Re: xfstest generic/020 failure on nojournal in ext4 dev branch

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

Date:	Tue, 1 Apr 2014 19:40:06 -0400
From:	Theodore Ts'o <tytso@....edu>
To:	Eric Whitney <enwlinux@...il.com>
Cc:	linux-ext4@...r.kernel.org
Subject: Re: xfstest generic/020 failure on nojournal in ext4 dev branch

On Tue, Apr 01, 2014 at 05:20:43PM -0400, Eric Whitney wrote:
> I'm seeing a problem in the dev branch when running xfstests on a non-journaled
> filesystem.  (All the other xfstests-bld scenarios are looking good in
> comparison with my 3.14 baseline.)
> 
> The test in question is generic/020, and it simply causes a BUG (null pointer
> dereference) that stops the test run.  Tip of my dev branch is 2c74cd642a.
> The last commits on there look like possible candidates given the stack trace.

Thanks for noticing this!

It was caused by a patch hunk in the patch each-fs-uses-its-own-mbcache
landing in the wrong place.  I've fixed up the patch and pushed out an
updated dev branch.

					- 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