linux-ext4 - Re: 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-prev] [day] [month] [year] [list]

Message-ID: <YxYOzsbUw/TDGRsL@mit.edu>
Date:   Mon, 5 Sep 2022 10:59:27 -0400
From:   "Theodore Ts'o" <tytso@....edu>
To:     Eric Whitney <enwlinux@...il.com>
Cc:     linux-ext4@...r.kernel.org
Subject: Re: kvm-xfstests, adv test scenario, inode size-related failures

On Sun, Sep 04, 2022 at 04:09:53PM -0400, Eric Whitney wrote:
> 
> 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)....

Whoops, thanks for reporting this.

What happened was that in the previous version of the test apppliance,
we were using a test version of e2fsprogs which was built from master
branch.  I built the kvm-xfstests images on a new build system, and it
was missing the bleedging-edge versions of e2fsprogs in the override
debs directory, so the image was using the Debian Stable (Bullseye)
version of e2fsprogs which is based on 1.46.2.  The Bullseyes/Backport
version of e2fsprogs is based on 1.46.5 and it would work fine.

Unfortunately, the package list for gce-xfstests and kvm-xfstests are
specified spearately, and while I had forced gce-xfstests to use the
backports version for e2fsprogs, I hadn't done so for kvm-xfstests.

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

I've fixed this in xfstests-bld:

commit 23020e266941c73928563554627a713d92462e70
Author: Theodore Ts'o <tytso@....edu>
Date:   Mon Sep 5 09:10:46 2022 -0400

    test-appliance: install e2fsprogs from bullseye/backports in kvm-xfstests

    Signed-off-by: Theodore Ts'o <tytso@....edu>

But if you can just use the workaround of using "kvm-xfstests maint"
to edit the /etc/mke2fs.conf file, that's probably the best short-term
solution, since I hope to re-release new test appliances with the
latest e2fsprogs 1.46.0-rc0 shortly.  This will enable the "adv2" test
case, and ultimately, once we get 1.46.0 into bullseye/backports, I'll
probably change the adv test case to include the orphan_file feature
and make adv2 an alias for adv.

Cheers,

					- Ted