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: <CAGW2f1Hdv42u=yHoFVhmx72z88gyNUC4MbQQ0UGk8BceNNEbGA@mail.gmail.com>
Date:	Wed, 8 Jan 2014 04:56:19 +0000
From:	jon ernst <jonernst07@...il.com>
To:	"Verma, Vishal L" <vishal.l.verma@...el.com>
Cc:	"linux-ext4@...r.kernel.org" <linux-ext4@...r.kernel.org>,
	"matthew@....cx" <matthew@....cx>
Subject: Re: xfstests failures in v3.13-rc7

Vishal,

I am ext4 newbie. Though I could share my experience about test 013 failure.
Make sure you have latest (or 1.42.9) e2fsck installed on your system.

Notice that v1.42.8 will cause 013 fail due to this:
http://comments.gmane.org/gmane.comp.file-systems.ext4/39980

To confirm my guess, you can check your xfstest full log to see if
e2fsck fail or not.


Just my idea. Could be wrong. Please correct me.

Best,
Jon

On Tue, Jan 7, 2014 at 2:57 AM, Verma, Vishal L
<vishal.l.verma@...el.com> wrote:
> Hi,
>
> I have been running xfstests with ext4 on a ramdisk (brd), and noticed a
> few tests were failing with an inconsistent file system at the end of
> the test.
>
> The following fail for v3.13-rc7:
> generic/013
> generic/083
> generic/269
> generic/321 (this one is not inconsistent fs, see log)
> generic/322
>
> The output of xfstests for these failures is also attached.
>
> It looks like generic/013 should be resolved by:
> http://thread.gmane.org/gmane.comp.file-systems.ext4/42032
> Are any of the others known failures, especially for brd?
>
> Thanks,
>         -Vishal
>
--
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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ