linux-ext4 - Re: ext4 v6.15-rc2 baseline

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: <20250417183711.GB6008@mit.edu>
Date: Thu, 17 Apr 2025 13:37:11 -0500
From: "Theodore Ts'o" <tytso@....edu>
To: "Darrick J. Wong" <djwong@...nel.org>
Cc: Luis Chamberlain <mcgrof@...nel.org>, adilger.kernel@...ger.ca,
        linux-ext4@...r.kernel.org, kdevops@...ts.linux.dev, dave@...olabs.net,
        jack@...e.cz
Subject: Re: ext4 v6.15-rc2 baseline

On Thu, Apr 17, 2025 at 09:38:20AM -0700, Darrick J. Wong wrote:
> 
> generic/04[456] fail with a bunch of...

Yeah, this is known.   I have an ext4-specific exclude file:

// generic/04[456] tests how truncate and delayed allocation works
// ext4 uses the data=ordered to avoid exposing stale data, and
// so it uses a different mechanism than xfs.  So these tests will fail
generic/044
generic/045
generic/046

> ext4/043 seems to fail because it tries to create 128b inodes with
> project ids and fails.

Yeah, I don't enable project id quotas by default in my test setups.

And _scratch_mkfs will fallback to using just the tests's mkfs option,
so if -O quota,project are specified in MKFS_OPTS, then the fallback works:

Start test timestamps with 128 inode size one device /dev/vdc
** mkfs failed with extra mkfs options added to "-q -O quota,project" by test 043 **
** attempting to mkfs using only test 043 options: -I 128 **

I suppose we could explicitly add something like -O ^project to the
test, but enabling -O project isn't in the default e2fsprogs
mke2fs.conf, and there are probably all sorts of oddball mke2fs.conf
configurations that might cause tesets to fail.

> ext4/053 I suspect fails because built-in quota conflicts with the quota
> mount options.

Hmm, I can't reproduce this with "kvm-xfstests -c ext4/quota
ext4/053", which will configure xfstests with:

MKFS_OPTIONS  -- -F -q -O quota,project /dev/vdc
MOUNT_OPTIONS -- -o acl,user_xattr -o block_validity /dev/vdc /vdc

Can you send me the out.bad and full files for that test?

Hmm... maybe this is another one of these "it fails if a non-standard
mke2fs.conf is used, although I don't see how."

> generic/{633,697,696} fails with:
> 
> --- /run/fstests/bin/tests/generic/697.out	2025-01-30 10:00:16.953276275 -0800
> +++ /var/tmp/fstests/generic/697.out.bad	2025-04-16 15:54:39.173837150 -0700
> @@ -1,2 +1,4 @@
>  QA output created by 697
> +utils.c: 928: openat_tmpfile_supported - Invalid argument - failure: create
> +utils.c: 928: openat_tmpfile_supported - Invalid argument - failure: create
>  Silence is golden
> 
> No idea what that's about.

I don't have any idea either.  I assume there's nothing in the dmesg
for that test?  Those tests are passing for me, so I got nothing.

    	 	      	    		    - Ted