linux-ext4 - latest xfstests-bld and nojournal test failures

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 for Android: free password hash cracker in your pocket

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

Message-ID: <20160816214519.GA18888@localhost.localdomain>
Date:	Tue, 16 Aug 2016 17:45:19 -0400
From:	Eric Whitney <enwlinux@...il.com>
To:	linux-ext4@...r.kernel.org
Cc:	tytso@....edu
Subject: latest xfstests-bld and nojournal test failures

FYI for those running the latest version of the test appliance:

Commit 5e574181f3bf ("test appliance - automate selection of
test/scratch devices") deleted the ^has_journal option from the
MKFS_OPTIONS string in the configuration file for the nojournal test
case.  This leads to failures for generic/034 and 18 other tests in the
nojournal test case;  all of them were prevented from running in the 
previous version of the test appliance by the xfstest function
_require_metadata_journaling().

That function determines whether a test file system supports metadata
journaling by using dumpe2fs to see whether the test or scratch file
system contains a journal.  Use of the noload mount option as
specified by EXT_MOUNT_OPTIONS doesn't affect that determination.

It looks like we'll want to add code to _require_metadata_journaling to
check for use of the noload mount option as well as presence/absence of a
journal.

Eric
--
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