From: "Darrick J. Wong" <djwong@kernel.org>
To: Theodore Ts'o <tytso@mit.edu>
Cc: Luis Chamberlain <mcgrof@kernel.org>,
adilger.kernel@dilger.ca, linux-ext4@vger.kernel.org,
kdevops@lists.linux.dev, dave@stgolabs.net, jack@suse.cz
Subject: Re: ext4 v6.15-rc2 baseline
Date: Thu, 17 Apr 2025 09:38:20 -0700 [thread overview]
Message-ID: <20250417163820.GA25655@frogsfrogsfrogs> (raw)
In-Reply-To: <20250416233415.GA3779528@mit.edu>
On Wed, Apr 16, 2025 at 06:34:15PM -0500, Theodore Ts'o wrote:
> TESTRUNID: ltm-20250414133140
> KERNEL: kernel 6.15.0-rc2-xfstests #22 SMP PREEMPT_DYNAMIC Mon Apr 14 12:18:46 EDT 2025 x86_64
> CMDLINE: --kernel gs://gce-xfstests/kernel.deb -c ext4/all -g auto
> CPUS: 2
> MEM: 7680
>
> ext4/4k: 587 tests, 55 skipped, 5340 seconds
Hum. My tests show:
Kernel: 6.15.0-rc2-xfsx
Format: mkfs.ext4
Mount: -o acl,user_xattr
Testing: -r -g all -x dangerous_fuzzers,recoveryloop,broken,deprecated
Failures: generic/045, generic/046, ext4/043, ext4/053, generic/697, generic/633, generic/696, generic/044
Status: Failed 8 of 553 (1.4%) tests, covering 40% of 2,077 in 2.2 hours.
mke2fs.conf has:
[defaults]
base_features = sparse_super,filetype,resize_inode,dir_index,ext_attr
default_mntopts = acl,user_xattr,block_validity
enable_periodic_fsck = 0
blocksize = 4096
cluster_size = 32768
inode_size = 256
inode_ratio = 16384
[fs_types]
ext2 = {
inode_size = 128
}
ext3 = {
features = has_journal
inode_size = 128
}
ext4 = {
features = has_journal,extent,huge_file,flex_bg,uninit_bg,dir_nlink,extra_isize,64bit,metadata_csum,quota
inode_size = 256
quotatype=usrquota:grpquota:prjquota:
}
generic/04[456] fail with a bunch of:
--- /run/fstests/bin/tests/generic/045.out 2025-01-30 10:00:16.774276934 -0800
+++ /var/tmp/fstests/generic/045.out.bad 2025-04-16 14:44:41.434069835 -0700
@@ -1 +1,1000 @@
QA output created by 045
+corrupt file /opt/1 - non-zero size but no extents
+corrupt file /opt/2 - non-zero size but no extents
+corrupt file /opt/3 - non-zero size but no extents
+corrupt file /opt/4 - non-zero size but no extents
ext4/043 seems to fail because it tries to create 128b inodes with
project ids and fails.
ext4/053 I suspect fails because built-in quota conflicts with the quota
mount options.
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.
--D
next prev parent reply other threads:[~2025-04-17 16:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-16 17:56 ext4 v6.15-rc2 baseline Luis Chamberlain
2025-04-16 23:34 ` Theodore Ts'o
2025-04-17 16:38 ` Darrick J. Wong [this message]
2025-04-17 18:37 ` Theodore Ts'o
2025-04-17 20:56 ` Luis Chamberlain
2025-04-19 18:22 ` Theodore Ts'o
2025-04-21 15:54 ` Darrick J. Wong
2025-04-21 16:29 ` Theodore Ts'o
2025-04-21 16:47 ` Darrick J. Wong
2025-04-17 16:49 ` Theodore Ts'o
2025-04-17 20:35 ` Luis Chamberlain
2025-04-18 1:42 ` Luis Chamberlain
2025-04-18 3:56 ` Theodore Ts'o
2025-04-18 19:08 ` Luis Chamberlain
2025-04-19 18:36 ` Theodore Ts'o
2025-04-20 3:39 ` Theodore Ts'o
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250417163820.GA25655@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=adilger.kernel@dilger.ca \
--cc=dave@stgolabs.net \
--cc=jack@suse.cz \
--cc=kdevops@lists.linux.dev \
--cc=linux-ext4@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=tytso@mit.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox