* [PATCH v2] README: add supported fs list
@ 2025-03-28 16:46 Zorro Lang
2025-04-12 6:26 ` Zorro Lang
` (2 more replies)
0 siblings, 3 replies; 6+ messages in thread
From: Zorro Lang @ 2025-03-28 16:46 UTC (permalink / raw)
To: fstests; +Cc: David Sterba, linux-fsdevel
To clarify the supported filesystems by fstests, add a fs list to
README file.
Signed-off-by: Zorro Lang <zlang@kernel.org>
Acked-by: "Darrick J. Wong" <djwong@kernel.org>
---
The v1 patch and review points:
https://lore.kernel.org/fstests/20250227200514.4085734-1-zlang@kernel.org/
V2 did below things:
1) Fix some wrong english sentences
2) Explain the meaning of "+" and "-".
3) Add a link to btrfs comment.
4) Split ext2/3/4 to 3 lines.
5) Reorder the fs list by "Level".
Thanks,
Zorro
README | 90 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
1 file changed, 90 insertions(+)
diff --git a/README b/README
index 024d39531..5ceaa0c1e 100644
--- a/README
+++ b/README
@@ -1,3 +1,93 @@
+_______________________
+SUPPORTED FS LIST
+_______________________
+
+History
+-------
+
+Firstly, xfstests is the old name of this project, due to it was originally
+developed for testing the XFS file system on the SGI's Irix operating system.
+When xfs was ported to Linux, so was xfstests, now it only supports Linux.
+
+As xfstests has many test cases that can be run on some other filesystems,
+we call them "generic" (and "shared", but it has been removed) cases, you
+can find them in tests/generic/ directory. Then more and more filesystems
+started to use xfstests, and contribute patches. Today xfstests is used
+as a file system regression test suite for lots of Linux's major file systems.
+So it's not "xfs"tests only, we tend to call it "fstests" now.
+
+Supported fs
+------------
+
+Firstly, there's not hard restriction about which filesystem can use fstests.
+Any filesystem can give fstests a try.
+
+Although fstests supports many filesystems, they have different support level
+by fstests. So mark it with 4 levels as below:
+
+L1: Fstests can be run on the specified fs basically.
+L2: Rare support from the specified fs list to fix some generic test failures.
+L3: Normal support from the specified fs list, has some own cases.
+L4: Active support from the fs list, has lots of own cases.
+
+("+" means a slightly higher than the current level, but not reach to the next.
+"-" is opposite, means a little bit lower than the current level.)
+
++------------+-------+---------------------------------------------------------+
+| Filesystem | Level | Comment |
++------------+-------+---------------------------------------------------------+
+| XFS | L4+ | N/A |
++------------+-------+---------------------------------------------------------+
+| Btrfs | L4 | https://btrfs.readthedocs.io/en/latest/dev/Development-\|
+| | | notes.html#fstests-setup |
++------------+-------+---------------------------------------------------------+
+| Ext4 | L4 | N/A |
++------------+-------+---------------------------------------------------------+
+| Ext2 | L3 | N/A |
++------------+-------+---------------------------------------------------------+
+| Ext3 | L3 | N/A |
++------------+-------+---------------------------------------------------------+
+| overlay | L3 | N/A |
++------------+-------+---------------------------------------------------------+
+| f2fs | L3- | N/A |
++------------+-------+---------------------------------------------------------+
+| tmpfs | L3- | N/A |
++------------+-------+---------------------------------------------------------+
+| NFS | L2+ | https://linux-nfs.org/wiki/index.php/Xfstests |
++------------+-------+---------------------------------------------------------+
+| Ceph | L2 | N/A |
++------------+-------+---------------------------------------------------------+
+| CIFS | L2- | https://wiki.samba.org/index.php/Xfstesting-cifs |
++------------+-------+---------------------------------------------------------+
+| ocfs2 | L2- | N/A |
++------------+-------+---------------------------------------------------------+
+| Bcachefs | L1+ | N/A |
++------------+-------+---------------------------------------------------------+
+| Exfat | L1+ | N/A |
++------------+-------+---------------------------------------------------------+
+| AFS | L1 | N/A |
++------------+-------+---------------------------------------------------------+
+| FUSE | L1 | N/A |
++------------+-------+---------------------------------------------------------+
+| GFS2 | L1 | N/A |
++------------+-------+---------------------------------------------------------+
+| Glusterfs | L1 | N/A |
++------------+-------+---------------------------------------------------------+
+| JFS | L1 | N/A |
++------------+-------+---------------------------------------------------------+
+| pvfs2 | L1 | N/A |
++------------+-------+---------------------------------------------------------+
+| Reiser4 | L1 | Reiserfs has been removed, only left reiser4 |
++------------+-------+---------------------------------------------------------+
+| ubifs | L1 | N/A |
++------------+-------+---------------------------------------------------------+
+| udf | L1 | N/A |
++------------+-------+---------------------------------------------------------+
+| Virtiofs | L1 | N/A |
++------------+-------+---------------------------------------------------------+
+| 9p | L1 | N/A |
++------------+-------+---------------------------------------------------------+
+
_______________________
BUILDING THE FSQA SUITE
_______________________
--
2.47.1
^ permalink raw reply related [flat|nested] 6+ messages in thread
* Re: [PATCH v2] README: add supported fs list
2025-03-28 16:46 [PATCH v2] README: add supported fs list Zorro Lang
@ 2025-04-12 6:26 ` Zorro Lang
2025-04-12 22:54 ` Anand Jain
2025-04-13 21:56 ` Kent Overstreet
2 siblings, 0 replies; 6+ messages in thread
From: Zorro Lang @ 2025-04-12 6:26 UTC (permalink / raw)
To: Zorro Lang; +Cc: fstests, David Sterba, linux-fsdevel
On Sat, Mar 29, 2025 at 12:46:09AM +0800, Zorro Lang wrote:
> To clarify the supported filesystems by fstests, add a fs list to
> README file.
>
> Signed-off-by: Zorro Lang <zlang@kernel.org>
> Acked-by: "Darrick J. Wong" <djwong@kernel.org>
> ---
>
> The v1 patch and review points:
> https://lore.kernel.org/fstests/20250227200514.4085734-1-zlang@kernel.org/
>
> V2 did below things:
> 1) Fix some wrong english sentences
> 2) Explain the meaning of "+" and "-".
> 3) Add a link to btrfs comment.
> 4) Split ext2/3/4 to 3 lines.
> 5) Reorder the fs list by "Level".
Any more review points on this patch? If no more, I'll merge it as it got
an ACK at least. We still can update it later if anyone need.
Thanks,
Zorro
>
> Thanks,
> Zorro
>
> README | 90 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 90 insertions(+)
>
> diff --git a/README b/README
> index 024d39531..5ceaa0c1e 100644
> --- a/README
> +++ b/README
> @@ -1,3 +1,93 @@
> +_______________________
> +SUPPORTED FS LIST
> +_______________________
> +
> +History
> +-------
> +
> +Firstly, xfstests is the old name of this project, due to it was originally
> +developed for testing the XFS file system on the SGI's Irix operating system.
> +When xfs was ported to Linux, so was xfstests, now it only supports Linux.
> +
> +As xfstests has many test cases that can be run on some other filesystems,
> +we call them "generic" (and "shared", but it has been removed) cases, you
> +can find them in tests/generic/ directory. Then more and more filesystems
> +started to use xfstests, and contribute patches. Today xfstests is used
> +as a file system regression test suite for lots of Linux's major file systems.
> +So it's not "xfs"tests only, we tend to call it "fstests" now.
> +
> +Supported fs
> +------------
> +
> +Firstly, there's not hard restriction about which filesystem can use fstests.
> +Any filesystem can give fstests a try.
> +
> +Although fstests supports many filesystems, they have different support level
> +by fstests. So mark it with 4 levels as below:
> +
> +L1: Fstests can be run on the specified fs basically.
> +L2: Rare support from the specified fs list to fix some generic test failures.
> +L3: Normal support from the specified fs list, has some own cases.
> +L4: Active support from the fs list, has lots of own cases.
> +
> +("+" means a slightly higher than the current level, but not reach to the next.
> +"-" is opposite, means a little bit lower than the current level.)
> +
> ++------------+-------+---------------------------------------------------------+
> +| Filesystem | Level | Comment |
> ++------------+-------+---------------------------------------------------------+
> +| XFS | L4+ | N/A |
> ++------------+-------+---------------------------------------------------------+
> +| Btrfs | L4 | https://btrfs.readthedocs.io/en/latest/dev/Development-\|
> +| | | notes.html#fstests-setup |
> ++------------+-------+---------------------------------------------------------+
> +| Ext4 | L4 | N/A |
> ++------------+-------+---------------------------------------------------------+
> +| Ext2 | L3 | N/A |
> ++------------+-------+---------------------------------------------------------+
> +| Ext3 | L3 | N/A |
> ++------------+-------+---------------------------------------------------------+
> +| overlay | L3 | N/A |
> ++------------+-------+---------------------------------------------------------+
> +| f2fs | L3- | N/A |
> ++------------+-------+---------------------------------------------------------+
> +| tmpfs | L3- | N/A |
> ++------------+-------+---------------------------------------------------------+
> +| NFS | L2+ | https://linux-nfs.org/wiki/index.php/Xfstests |
> ++------------+-------+---------------------------------------------------------+
> +| Ceph | L2 | N/A |
> ++------------+-------+---------------------------------------------------------+
> +| CIFS | L2- | https://wiki.samba.org/index.php/Xfstesting-cifs |
> ++------------+-------+---------------------------------------------------------+
> +| ocfs2 | L2- | N/A |
> ++------------+-------+---------------------------------------------------------+
> +| Bcachefs | L1+ | N/A |
> ++------------+-------+---------------------------------------------------------+
> +| Exfat | L1+ | N/A |
> ++------------+-------+---------------------------------------------------------+
> +| AFS | L1 | N/A |
> ++------------+-------+---------------------------------------------------------+
> +| FUSE | L1 | N/A |
> ++------------+-------+---------------------------------------------------------+
> +| GFS2 | L1 | N/A |
> ++------------+-------+---------------------------------------------------------+
> +| Glusterfs | L1 | N/A |
> ++------------+-------+---------------------------------------------------------+
> +| JFS | L1 | N/A |
> ++------------+-------+---------------------------------------------------------+
> +| pvfs2 | L1 | N/A |
> ++------------+-------+---------------------------------------------------------+
> +| Reiser4 | L1 | Reiserfs has been removed, only left reiser4 |
> ++------------+-------+---------------------------------------------------------+
> +| ubifs | L1 | N/A |
> ++------------+-------+---------------------------------------------------------+
> +| udf | L1 | N/A |
> ++------------+-------+---------------------------------------------------------+
> +| Virtiofs | L1 | N/A |
> ++------------+-------+---------------------------------------------------------+
> +| 9p | L1 | N/A |
> ++------------+-------+---------------------------------------------------------+
> +
> _______________________
> BUILDING THE FSQA SUITE
> _______________________
> --
> 2.47.1
>
>
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [PATCH v2] README: add supported fs list
2025-03-28 16:46 [PATCH v2] README: add supported fs list Zorro Lang
2025-04-12 6:26 ` Zorro Lang
@ 2025-04-12 22:54 ` Anand Jain
2025-04-13 21:56 ` Kent Overstreet
2 siblings, 0 replies; 6+ messages in thread
From: Anand Jain @ 2025-04-12 22:54 UTC (permalink / raw)
To: Zorro Lang, fstests; +Cc: David Sterba, linux-fsdevel
On 29/3/25 00:46, Zorro Lang wrote:
> To clarify the supported filesystems by fstests, add a fs list to
> README file.
>
> Signed-off-by: Zorro Lang <zlang@kernel.org>
> Acked-by: "Darrick J. Wong" <djwong@kernel.org>
> ---
>
> The v1 patch and review points:
> https://lore.kernel.org/fstests/20250227200514.4085734-1-zlang@kernel.org/
>
> V2 did below things:
> 1) Fix some wrong english sentences
> 2) Explain the meaning of "+" and "-".
> 3) Add a link to btrfs comment.
> 4) Split ext2/3/4 to 3 lines.
> 5) Reorder the fs list by "Level".
>
> Thanks,
> Zorro
>
> README | 90 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 90 insertions(+)
>
> diff --git a/README b/README
> index 024d39531..5ceaa0c1e 100644
> --- a/README
> +++ b/README
> @@ -1,3 +1,93 @@
> +_______________________
> +SUPPORTED FS LIST
> +_______________________
> +
> +History
> +-------
> +
> +Firstly, xfstests is the old name of this project, due to it was originally
> +developed for testing the XFS file system on the SGI's Irix operating system.
> +When xfs was ported to Linux, so was xfstests, now it only supports Linux.
> +
> +As xfstests has many test cases that can be run on some other filesystems,
> +we call them "generic" (and "shared", but it has been removed) cases, you
> +can find them in tests/generic/ directory. Then more and more filesystems
> +started to use xfstests, and contribute patches. Today xfstests is used
> +as a file system regression test suite for lots of Linux's major file systems.
> +So it's not "xfs"tests only, we tend to call it "fstests" now.
> +
> +Supported fs
> +------------
> +
> +Firstly, there's not hard restriction about which filesystem can use fstests.
> +Any filesystem can give fstests a try.
> +
> +Although fstests supports many filesystems, they have different support level
> +by fstests. So mark it with 4 levels as below:
> +
> +L1: Fstests can be run on the specified fs basically.
> +L2: Rare support from the specified fs list to fix some generic test failures.
> +L3: Normal support from the specified fs list, has some own cases.
> +L4: Active support from the fs list, has lots of own cases.
> +
> +("+" means a slightly higher than the current level, but not reach to the next.
> +"-" is opposite, means a little bit lower than the current level.)
So far, we’ve defined only four levels: L1, L2, L3, and L4.
The "+" suggests a transition to the next level.
But when it comes to L4+, what’s next — L5? If so, then we’re
missing a clear definition for L5.
Thx. Anand
> +
> ++------------+-------+---------------------------------------------------------+
> +| Filesystem | Level | Comment |
> ++------------+-------+---------------------------------------------------------+
> +| XFS | L4+ | N/A |
> ++------------+-------+---------------------------------------------------------+
> +| Btrfs | L4 | https://btrfs.readthedocs.io/en/latest/dev/Development-\|
> +| | | notes.html#fstests-setup |
> ++------------+-------+---------------------------------------------------------+
> +| Ext4 | L4 | N/A |
> ++------------+-------+---------------------------------------------------------+
> +| Ext2 | L3 | N/A |
> ++------------+-------+---------------------------------------------------------+
> +| Ext3 | L3 | N/A |
> ++------------+-------+---------------------------------------------------------+
> +| overlay | L3 | N/A |
> ++------------+-------+---------------------------------------------------------+
> +| f2fs | L3- | N/A |
> ++------------+-------+---------------------------------------------------------+
> +| tmpfs | L3- | N/A |
> ++------------+-------+---------------------------------------------------------+
> +| NFS | L2+ | https://linux-nfs.org/wiki/index.php/Xfstests |
> ++------------+-------+---------------------------------------------------------+
> +| Ceph | L2 | N/A |
> ++------------+-------+---------------------------------------------------------+
> +| CIFS | L2- | https://wiki.samba.org/index.php/Xfstesting-cifs |
> ++------------+-------+---------------------------------------------------------+
> +| ocfs2 | L2- | N/A |
> ++------------+-------+---------------------------------------------------------+
> +| Bcachefs | L1+ | N/A |
> ++------------+-------+---------------------------------------------------------+
> +| Exfat | L1+ | N/A |
> ++------------+-------+---------------------------------------------------------+
> +| AFS | L1 | N/A |
> ++------------+-------+---------------------------------------------------------+
> +| FUSE | L1 | N/A |
> ++------------+-------+---------------------------------------------------------+
> +| GFS2 | L1 | N/A |
> ++------------+-------+---------------------------------------------------------+
> +| Glusterfs | L1 | N/A |
> ++------------+-------+---------------------------------------------------------+
> +| JFS | L1 | N/A |
> ++------------+-------+---------------------------------------------------------+
> +| pvfs2 | L1 | N/A |
> ++------------+-------+---------------------------------------------------------+
> +| Reiser4 | L1 | Reiserfs has been removed, only left reiser4 |
> ++------------+-------+---------------------------------------------------------+
> +| ubifs | L1 | N/A |
> ++------------+-------+---------------------------------------------------------+
> +| udf | L1 | N/A |
> ++------------+-------+---------------------------------------------------------+
> +| Virtiofs | L1 | N/A |
> ++------------+-------+---------------------------------------------------------+
> +| 9p | L1 | N/A |
> ++------------+-------+---------------------------------------------------------+
> +
> _______________________
> BUILDING THE FSQA SUITE
> _______________________
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [PATCH v2] README: add supported fs list
2025-03-28 16:46 [PATCH v2] README: add supported fs list Zorro Lang
2025-04-12 6:26 ` Zorro Lang
2025-04-12 22:54 ` Anand Jain
@ 2025-04-13 21:56 ` Kent Overstreet
2025-04-14 5:58 ` Zorro Lang
2 siblings, 1 reply; 6+ messages in thread
From: Kent Overstreet @ 2025-04-13 21:56 UTC (permalink / raw)
To: Zorro Lang; +Cc: fstests, David Sterba, linux-fsdevel
On Sat, Mar 29, 2025 at 12:46:09AM +0800, Zorro Lang wrote:
> To clarify the supported filesystems by fstests, add a fs list to
> README file.
>
> Signed-off-by: Zorro Lang <zlang@kernel.org>
> Acked-by: "Darrick J. Wong" <djwong@kernel.org>
> ---
>
> The v1 patch and review points:
> https://lore.kernel.org/fstests/20250227200514.4085734-1-zlang@kernel.org/
>
> V2 did below things:
> 1) Fix some wrong english sentences
> 2) Explain the meaning of "+" and "-".
> 3) Add a link to btrfs comment.
> 4) Split ext2/3/4 to 3 lines.
> 5) Reorder the fs list by "Level".
>
> Thanks,
> Zorro
>
> README | 90 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 90 insertions(+)
>
> diff --git a/README b/README
> index 024d39531..5ceaa0c1e 100644
> --- a/README
> +++ b/README
> @@ -1,3 +1,93 @@
> +_______________________
> +SUPPORTED FS LIST
> +_______________________
> +
> +History
> +-------
> +
> +Firstly, xfstests is the old name of this project, due to it was originally
> +developed for testing the XFS file system on the SGI's Irix operating system.
> +When xfs was ported to Linux, so was xfstests, now it only supports Linux.
> +
> +As xfstests has many test cases that can be run on some other filesystems,
> +we call them "generic" (and "shared", but it has been removed) cases, you
> +can find them in tests/generic/ directory. Then more and more filesystems
> +started to use xfstests, and contribute patches. Today xfstests is used
> +as a file system regression test suite for lots of Linux's major file systems.
> +So it's not "xfs"tests only, we tend to call it "fstests" now.
> +
> +Supported fs
> +------------
> +
> +Firstly, there's not hard restriction about which filesystem can use fstests.
> +Any filesystem can give fstests a try.
> +
> +Although fstests supports many filesystems, they have different support level
> +by fstests. So mark it with 4 levels as below:
> +
> +L1: Fstests can be run on the specified fs basically.
> +L2: Rare support from the specified fs list to fix some generic test failures.
> +L3: Normal support from the specified fs list, has some own cases.
> +L4: Active support from the fs list, has lots of own cases.
> +
> +("+" means a slightly higher than the current level, but not reach to the next.
> +"-" is opposite, means a little bit lower than the current level.)
> +
> ++------------+-------+---------------------------------------------------------+
> +| Filesystem | Level | Comment |
> ++------------+-------+---------------------------------------------------------+
> +| XFS | L4+ | N/A |
> ++------------+-------+---------------------------------------------------------+
> +| Btrfs | L4 | https://btrfs.readthedocs.io/en/latest/dev/Development-\|
> +| | | notes.html#fstests-setup |
> ++------------+-------+---------------------------------------------------------+
> +| Ext4 | L4 | N/A |
> ++------------+-------+---------------------------------------------------------+
> +| Ext2 | L3 | N/A |
> ++------------+-------+---------------------------------------------------------+
> +| Ext3 | L3 | N/A |
> ++------------+-------+---------------------------------------------------------+
> +| overlay | L3 | N/A |
> ++------------+-------+---------------------------------------------------------+
> +| f2fs | L3- | N/A |
> ++------------+-------+---------------------------------------------------------+
> +| tmpfs | L3- | N/A |
> ++------------+-------+---------------------------------------------------------+
> +| NFS | L2+ | https://linux-nfs.org/wiki/index.php/Xfstests |
> ++------------+-------+---------------------------------------------------------+
> +| Ceph | L2 | N/A |
> ++------------+-------+---------------------------------------------------------+
> +| CIFS | L2- | https://wiki.samba.org/index.php/Xfstesting-cifs |
> ++------------+-------+---------------------------------------------------------+
> +| ocfs2 | L2- | N/A |
> ++------------+-------+---------------------------------------------------------+
> +| Bcachefs | L1+ | N/A |
I heavily use xfstests and look at the test results every day - I
believe that would indicate L3.
bcachefs specific tests are not generally in fstests beacuse there's
lots of things that ktest can do that fstests can't, and I find it a bit
more modern (i.e. tests that names, not numbers)
Not all tests are passing (and won't be for awhile), but the remaining
stuff is non critical (i.e. fsync() error behaviour when the filesystem
has been shutdown, or certain device removal tests where the behaviour
could probably use some discussion.
But if you find e.g. a configuration that produces a generic/388 pop,
that would go to the top of the pile.
(I do have a few patches to the tests for bcachefs in my tree that I
really ought to get upstream).
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [PATCH v2] README: add supported fs list
2025-04-13 21:56 ` Kent Overstreet
@ 2025-04-14 5:58 ` Zorro Lang
2025-04-14 11:09 ` Kent Overstreet
0 siblings, 1 reply; 6+ messages in thread
From: Zorro Lang @ 2025-04-14 5:58 UTC (permalink / raw)
To: Kent Overstreet; +Cc: Zorro Lang, fstests, David Sterba, linux-fsdevel
On Sun, Apr 13, 2025 at 05:56:08PM -0400, Kent Overstreet wrote:
> On Sat, Mar 29, 2025 at 12:46:09AM +0800, Zorro Lang wrote:
> > To clarify the supported filesystems by fstests, add a fs list to
> > README file.
> >
> > Signed-off-by: Zorro Lang <zlang@kernel.org>
> > Acked-by: "Darrick J. Wong" <djwong@kernel.org>
> > ---
> >
> > The v1 patch and review points:
> > https://lore.kernel.org/fstests/20250227200514.4085734-1-zlang@kernel.org/
> >
> > V2 did below things:
> > 1) Fix some wrong english sentences
> > 2) Explain the meaning of "+" and "-".
> > 3) Add a link to btrfs comment.
> > 4) Split ext2/3/4 to 3 lines.
> > 5) Reorder the fs list by "Level".
> >
> > Thanks,
> > Zorro
> >
> > README | 90 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> > 1 file changed, 90 insertions(+)
> >
> > diff --git a/README b/README
> > index 024d39531..5ceaa0c1e 100644
> > --- a/README
> > +++ b/README
> > @@ -1,3 +1,93 @@
> > +_______________________
> > +SUPPORTED FS LIST
> > +_______________________
> > +
> > +History
> > +-------
> > +
> > +Firstly, xfstests is the old name of this project, due to it was originally
> > +developed for testing the XFS file system on the SGI's Irix operating system.
> > +When xfs was ported to Linux, so was xfstests, now it only supports Linux.
> > +
> > +As xfstests has many test cases that can be run on some other filesystems,
> > +we call them "generic" (and "shared", but it has been removed) cases, you
> > +can find them in tests/generic/ directory. Then more and more filesystems
> > +started to use xfstests, and contribute patches. Today xfstests is used
> > +as a file system regression test suite for lots of Linux's major file systems.
> > +So it's not "xfs"tests only, we tend to call it "fstests" now.
> > +
> > +Supported fs
> > +------------
> > +
> > +Firstly, there's not hard restriction about which filesystem can use fstests.
> > +Any filesystem can give fstests a try.
> > +
> > +Although fstests supports many filesystems, they have different support level
> > +by fstests. So mark it with 4 levels as below:
> > +
> > +L1: Fstests can be run on the specified fs basically.
> > +L2: Rare support from the specified fs list to fix some generic test failures.
> > +L3: Normal support from the specified fs list, has some own cases.
> > +L4: Active support from the fs list, has lots of own cases.
> > +
> > +("+" means a slightly higher than the current level, but not reach to the next.
> > +"-" is opposite, means a little bit lower than the current level.)
> > +
> > ++------------+-------+---------------------------------------------------------+
> > +| Filesystem | Level | Comment |
> > ++------------+-------+---------------------------------------------------------+
> > +| XFS | L4+ | N/A |
> > ++------------+-------+---------------------------------------------------------+
> > +| Btrfs | L4 | https://btrfs.readthedocs.io/en/latest/dev/Development-\|
> > +| | | notes.html#fstests-setup |
> > ++------------+-------+---------------------------------------------------------+
> > +| Ext4 | L4 | N/A |
> > ++------------+-------+---------------------------------------------------------+
> > +| Ext2 | L3 | N/A |
> > ++------------+-------+---------------------------------------------------------+
> > +| Ext3 | L3 | N/A |
> > ++------------+-------+---------------------------------------------------------+
> > +| overlay | L3 | N/A |
> > ++------------+-------+---------------------------------------------------------+
> > +| f2fs | L3- | N/A |
> > ++------------+-------+---------------------------------------------------------+
> > +| tmpfs | L3- | N/A |
> > ++------------+-------+---------------------------------------------------------+
> > +| NFS | L2+ | https://linux-nfs.org/wiki/index.php/Xfstests |
> > ++------------+-------+---------------------------------------------------------+
> > +| Ceph | L2 | N/A |
> > ++------------+-------+---------------------------------------------------------+
> > +| CIFS | L2- | https://wiki.samba.org/index.php/Xfstesting-cifs |
> > ++------------+-------+---------------------------------------------------------+
> > +| ocfs2 | L2- | N/A |
> > ++------------+-------+---------------------------------------------------------+
> > +| Bcachefs | L1+ | N/A |
>
> I heavily use xfstests and look at the test results every day - I
> believe that would indicate L3.
Glad to receive the response from bcachefs :) L3 means there're enough fs specific
test cases in tests/$FSTYP besides generic cases, e.g. tests/overlay, or f2fs (although
it only has a few currently, but it's increasing).
>
> bcachefs specific tests are not generally in fstests beacuse there's
> lots of things that ktest can do that fstests can't, and I find it a bit
> more modern (i.e. tests that names, not numbers)
ktest? linux/tools/testing/ktest/ ? I'm glad to learn about more test suites,
I run fstests and LTP and some others too, fstests can't cover everything :)
Hmm... about the names... fstests supports to append a name to the ID number,
but the developers (looks like) prefer using number only all the time, then
it become a "tradition" now.
>
> Not all tests are passing (and won't be for awhile), but the remaining
> stuff is non critical (i.e. fsync() error behaviour when the filesystem
> has been shutdown, or certain device removal tests where the behaviour
> could probably use some discussion.
>
> But if you find e.g. a configuration that produces a generic/388 pop,
> that would go to the top of the pile.
>
> (I do have a few patches to the tests for bcachefs in my tree that I
> really ought to get upstream).
Sure, warm welcome your patches. And don't worry, you can send patch to
update the level part anytime when you think fstests supports becachefs
more :)
Thanks,
Zorro
>
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [PATCH v2] README: add supported fs list
2025-04-14 5:58 ` Zorro Lang
@ 2025-04-14 11:09 ` Kent Overstreet
0 siblings, 0 replies; 6+ messages in thread
From: Kent Overstreet @ 2025-04-14 11:09 UTC (permalink / raw)
To: Zorro Lang; +Cc: Zorro Lang, fstests, David Sterba, linux-fsdevel
On Mon, Apr 14, 2025 at 01:58:57PM +0800, Zorro Lang wrote:
> On Sun, Apr 13, 2025 at 05:56:08PM -0400, Kent Overstreet wrote:
> > I heavily use xfstests and look at the test results every day - I
> > believe that would indicate L3.
>
> Glad to receive the response from bcachefs :) L3 means there're enough fs specific
> test cases in tests/$FSTYP besides generic cases, e.g. tests/overlay, or f2fs (although
> it only has a few currently, but it's increasing).
Active support for existing tests, or writing new tests?
To be blunt, fstests is not a great environment for writing tests, the
'golden master' model of pass/failure means debugging test failures is
archaic.
But those tests do get run and used, with active support.
> > bcachefs specific tests are not generally in fstests beacuse there's
> > lots of things that ktest can do that fstests can't, and I find it a bit
> > more modern (i.e. tests that names, not numbers)
>
> ktest? linux/tools/testing/ktest/ ? I'm glad to learn about more test suites,
> I run fstests and LTP and some others too, fstests can't cover everything :)
> Hmm... about the names... fstests supports to append a name to the ID number,
> but the developers (looks like) prefer using number only all the time, then
> it become a "tradition" now.
No, not that. Does anyone even use that thing?
https://evilpiepirate.org/git/ktest.git/
It's a full CI - https://evilpiepirate.org/~testdashboard/ci
>
> >
> > Not all tests are passing (and won't be for awhile), but the remaining
> > stuff is non critical (i.e. fsync() error behaviour when the filesystem
> > has been shutdown, or certain device removal tests where the behaviour
> > could probably use some discussion.
> >
> > But if you find e.g. a configuration that produces a generic/388 pop,
> > that would go to the top of the pile.
> >
> > (I do have a few patches to the tests for bcachefs in my tree that I
> > really ought to get upstream).
>
> Sure, warm welcome your patches. And don't worry, you can send patch to
> update the level part anytime when you think fstests supports becachefs
> more :)
>
> Thanks,
> Zorro
>
> >
>
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2025-04-14 11:09 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2025-03-28 16:46 [PATCH v2] README: add supported fs list Zorro Lang
2025-04-12 6:26 ` Zorro Lang
2025-04-12 22:54 ` Anand Jain
2025-04-13 21:56 ` Kent Overstreet
2025-04-14 5:58 ` Zorro Lang
2025-04-14 11:09 ` Kent Overstreet
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox