linux-ext4 - Re: [PATCH] xfstests-bld: specify inode size in inline test scenario conf

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

Message-ID: <20140927181049.GA11222@thunk.org>
Date:	Sat, 27 Sep 2014 14:10:49 -0400
From:	Theodore Ts'o <tytso@....edu>
To:	Eric Whitney <enwlinux@...il.com>
Cc:	linux-ext4@...r.kernel.org
Subject: Re: [PATCH] xfstests-bld: specify inode size in inline test scenario
 conf

On Fri, Sep 26, 2014 at 06:16:46PM -0400, Eric Whitney wrote:
> Some xfstests use test file systems that are smaller than 512 MB, and
> per the mke2fs.conf default, contain 128 byte inodes.  These tests
> include xfstests generic/015, generic/077, generic/083, and shared/298.
> All of them fail at mkfs time when run in xfstest-bld's inline test
> scenario because the inline data feature requires a minimum inode size
> of 256 bytes.
> 
> Fix this problem by specifying an inode size of 256 bytes in the inline
> conf file.  This allows the tester more flexibility than modifying the
> xfstests themselves.
> 
> This change also makes it possible to run generic/027 successfully and
> in a reasonable amount of time (less than 20 minutes on one x86-64 VM).
> It also fails silently when mkfs'ing its test file system, but then
> proceeds to run and reports success erroneously.
> 
> Signed-off-by: Eric Whitney <enwlinux@...il.com>

Applied, thanks.

						- 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