From: "Theodore Tso" <tytso@mit.edu>
To: linux-fsdevel@vger.kernel.org, lsf-pc@lists.linux-foundation.org
Subject: [LSF/MM/BPF TOPIC] File system testing
Date: Wed, 18 Feb 2026 10:07:36 -0500 [thread overview]
Message-ID: <20260218150736.GD45984@macsyma-wired.lan> (raw)
I'd like to propose a perennial favorite file system testing as a
topic for the FS track. Topics to cover would include:
1) Standardizing test scenarios for various file systems.
I have test scenarios for ext4 and xfs in my test appliance (e.g.,
4k, 64k, and 1k blocksizes, with fscrypt enabled, with dax enabled,
etc.) But I don't have those for other file systems, such as
btrfs, etc. It would be nice if this could be centrally documented
some where, perhaps in the kernel sources?
2) Standardized way of expressing that certain tests are expected to
fail for a given test scenario. Ideally, we can encode this in
xfstests upstream (an example of this is requiring metadata
journalling for generic/388). But in some cases the failure is
very specific to a particular set of file system configurations,
and it may vary depending on kernel version (e.g., a problem that
was fixed in 6.6 and later LTS kernels, but it was too hard to
backport to earlier LTS kernels).
3) Automating the use of tests to validate file system backports to
LTS kernels, so that commits which might cause file system
regressions can be automatically dropped from a LTS rc kernel.
- Ted
next reply other threads:[~2026-02-18 15:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-18 15:07 Theodore Tso [this message]
2026-02-19 14:37 ` [LSF/MM/BPF TOPIC] File system testing Chuck Lever
2026-02-19 18:42 ` Ric Wheeler
2026-02-20 9:09 ` Hans Holmberg
2026-02-24 12:48 ` Carlos Maiolino
2026-02-25 18:40 ` [Lsf-pc] " Jan Kara
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=20260218150736.GD45984@macsyma-wired.lan \
--to=tytso@mit.edu \
--cc=linux-fsdevel@vger.kernel.org \
--cc=lsf-pc@lists.linux-foundation.org \
/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