linux-ext4 - kvm-xfstests, adv test scenario, inode size-related 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: Windows password security audit tool. GUI, reports in PDF.

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

Date:   Sun, 4 Sep 2022 16:09:53 -0400
From:   Eric Whitney <enwlinux@...il.com>
To:     tytso@....edu
Cc:     linux-ext4@...r.kernel.org
Subject: kvm-xfstests, adv test scenario, inode size-related failures

Hi Ted:

I'm seeing a large number of test failures running 6.0-rc3 on the latest
version of the test appliance in the adv test scenario.  All of these failures
share a common feature - mke2fs fails to create a scratch file system using the
inline option because the requested inode size is 128 bytes.  This didn't
occur on the previous version of the test appliance.

It looks like /etc/mke2fs.conf contains an extra relation for the "small"
stanza: "inode_size = 128".  This isn't present in mke2fs.conf in the
previous version of the test appliance, nor does it appear to be in the latest
master branch version of e2fsprogs (perhaps I'm looking in the wrong place).
Deleting that line from /etc/mke2fs.conf on the latest version of the test
appliance eliminates the failures (as does modifying ~/fs/ext4/conf/adv
to specify a 256 byte inode size in the list of mkfs options).  The previous
version of the test appliance applied the default mke2fs.conf value of 256
for the inode size, so mke2fs didn't reject the request there.

For reference, the tests that fail for me include:

ext4/021, /036, /038, /039, /048, /271

generic/015, /077, /081, /083, /085, /204, /226, /250, /252, /371, /399, /416,
/427, /449, /459, /500, /511, /619, /626

shared/298

Eric