From: Ethan Nelson-Moore <enelsonmoore@gmail.com>
To: Tony Luck <tony.luck@intel.com>,
"Guilherme G. Piccoli" <gpiccoli@igalia.com>,
Christian Brauner <brauner@kernel.org>,
Bhavik Sachdev <b.sachdev1904@gmail.com>,
linux-kselftest@vger.kernel.org
Cc: Ethan Nelson-Moore <enelsonmoore@gmail.com>,
Shuah Khan <shuah@kernel.org>, Kees Cook <kees@kernel.org>
Subject: [PATCH] selftests/statmount: update list of valid filesystems
Date: Sat, 5 Sep 2026 20:16:25 -0700 [thread overview]
Message-ID: <20260906031629.74204-1-enelsonmoore@gmail.com> (raw)
The list of valid filesystems in
tools/testing/selftests/filesystems/statmount/statmount_test.c contains
several filesystems that have been removed from the kernel, and is
missing several recently added filesystems. Update it.
The new list was generated using this small script:
(grep -rA10 'struct file_system_type .* =' | fgrep -w .name
fgrep -r MODULE_ALIAS_FS'(' | grep -v '#define'
) | cut -d '"' -f2 | LC_ALL=C sort -u | while read a; do
printf '"%s", ' "$a"
done
echo
It was then manually formatted and edited to remove filesystem types
registered by tests and fix a few entries the script couldn't extract
correctly.
Signed-off-by: Ethan Nelson-Moore <enelsonmoore@gmail.com>
---
.../filesystems/statmount/statmount_test.c | 24 +++++++++----------
1 file changed, 12 insertions(+), 12 deletions(-)
diff --git a/tools/testing/selftests/filesystems/statmount/statmount_test.c b/tools/testing/selftests/filesystems/statmount/statmount_test.c
index 52544512edc7..352ca022f248 100644
--- a/tools/testing/selftests/filesystems/statmount/statmount_test.c
+++ b/tools/testing/selftests/filesystems/statmount/statmount_test.c
@@ -17,21 +17,21 @@
static const char *const known_fs[] = {
"9p", "adfs", "affs", "afs", "aio", "anon_inodefs", "apparmorfs",
- "autofs", "bcachefs", "bdev", "befs", "binder", "binfmt_misc",
+ "autofs", "bdev", "befs", "binder", "binfmt_misc",
"bpf", "btrfs", "btrfs_test_fs", "ceph", "cgroup", "cgroup2", "cifs",
- "coda", "configfs", "cpuset", "cramfs", "cxl", "dax", "debugfs",
- "devpts", "devtmpfs", "dmabuf", "drm", "ecryptfs", "efivarfs", "efs",
- "erofs", "exfat", "ext2", "ext3", "ext4", "f2fs", "functionfs",
- "fuse", "fuseblk", "fusectl", "gadgetfs", "gfs2", "gfs2meta", "hfs",
- "hfsplus", "hostfs", "hpfs", "hugetlbfs", "ibmasmfs", "iomem",
- "ipathfs", "iso9660", "jffs2", "jfs", "minix", "mqueue", "msdos",
- "nfs", "nfs4", "nfsd", "nilfs2", "nsfs", "ntfs", "ntfs3", "ocfs2",
- "ocfs2_dlmfs", "omfs", "openpromfs", "overlay", "pipefs", "proc",
- "pstore", "pvfs2", "qnx4", "qnx6", "ramfs", "resctrl", "romfs",
+ "coda", "configfs", "cpuset", "cramfs", "dax", "debugfs",
+ "devpts", "devtmpfs", "dmabuf", "drm", "ecryptfs", "efivarfs",
+ "erofs", "exfat", "ext2", "ext3", "ext4", "f2fs", "failfs", "functionfs",
+ "fuse", "fuseblk", "fusectl", "gadgetfs", "gfs2", "gfs2meta", "guest_memfd", "hfs",
+ "hfsplus", "hostfs", "hpfs", "hugetlbfs", "iomem",
+ "iso9660", "jffs2", "jfs", "minix", "mqueue", "msdos",
+ "nfs", "nfs4", "nfsd", "nilfs2", "nsfs", "ntfs", "ntfs3", "nullfs", "ocfs2",
+ "ocfs2_dlmfs", "omfs", "openpromfs", "overlay", "pidfs", "pipefs", "proc",
+ "pseudo_erofs", "pstore", "pvfs2", "qnx4", "qnx6", "ramfs", "resctrl", "romfs",
"rootfs", "rpc_pipefs", "s390_hypfs", "secretmem", "securityfs",
"selinuxfs", "smackfs", "smb3", "sockfs", "spufs", "squashfs", "sysfs",
- "sysv", "tmpfs", "tracefs", "ubifs", "udf", "ufs", "v7", "vboxsf",
- "vfat", "virtiofs", "vxfs", "xenfs", "xfs", "zonefs", NULL };
+ "tmpfs", "tracefs", "ubifs", "udf", "ufs", "vboxsf",
+ "vfat", "vfio", "virtiofs", "xenfs", "xfs", "zonefs", NULL };
static void write_file(const char *path, const char *val)
{
--
2.43.0
reply other threads:[~2026-09-06 3:16 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20260906031629.74204-1-enelsonmoore@gmail.com \
--to=enelsonmoore@gmail.com \
--cc=b.sachdev1904@gmail.com \
--cc=brauner@kernel.org \
--cc=gpiccoli@igalia.com \
--cc=kees@kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=shuah@kernel.org \
--cc=tony.luck@intel.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.