FS/XFS testing framework
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <djwong@kernel.org>
To: Zorro Lang <zlang@redhat.com>
Cc: Zorro Lang <zlang@kernel.org>,
	fstests@vger.kernel.org, David Sterba <dsterba@suse.com>,
	linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] README: add supported fs list
Date: Thu, 27 Feb 2025 22:31:25 -0800	[thread overview]
Message-ID: <20250228063125.GC6225@frogsfrogsfrogs> (raw)
In-Reply-To: <20250228051600.b44dmfimqqbrom22@dell-per750-06-vm-08.rhts.eng.pek2.redhat.com>

On Fri, Feb 28, 2025 at 01:16:00PM +0800, Zorro Lang wrote:
> On Thu, Feb 27, 2025 at 06:20:45PM -0800, Darrick J. Wong wrote:
> > On Fri, Feb 28, 2025 at 04:05:14AM +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>
> > > ---
> > > 
> > > Hi,
> > > 
> > > David Sterba suggests to have a supported fs list in fstests:
> > > 
> > > https://lore.kernel.org/fstests/20250227073535.7gt7mj5gunp67axr@dell-per750-06-vm-08.rhts.eng.pek2.redhat.com/T/#m742e4f1f6668d39c1a48450e7176a366e0a2f6f9
> > > 
> > > I think that's a good suggestion, so I send this patch now. But tell the truth,
> > > it's hard to find all filesystems which are supported by fstests. Especially
> > > some filesystems might use fstests, but never be metioned in fstests code.
> > > So please review this patch or send another patch to tell fstests@ list, if
> > > you know any other filesystem is suppported.
> > > 
> > > And if anyone has review point about the support "level" and "comment" part,
> > > please feel free to tell me :)
> > > 
> > > Thanks,
> > > Zorro
> > > 
> > >  README | 82 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> > >  1 file changed, 82 insertions(+)
> > > 
> > > diff --git a/README b/README
> > > index 024d39531..055935917 100644
> > > --- a/README
> > > +++ b/README
> > > @@ -1,3 +1,85 @@
> > > +_______________________
> > > +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.
> > > +With xfs was ported to Linux, so was xfstests, now it only supports Linux.
> > 
> >    When
> > 
> > > +
> > > +As xfstests has some test cases are good to run on some other filesystems,
> > 
> >                    many test cases that can be run
> 
> Sure, will change these.
> 
> > 
> > > +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.
> > > +
> > > ++------------+-------+---------------------------------------------------------+
> > > +| Filesystem | Level |                       Comment                           |
> > > ++------------+-------+---------------------------------------------------------+
> > > +| AFS        |  L1   | N/A                                                     |
> > > ++------------+-------+---------------------------------------------------------+
> > > +| Bcachefs   |  L1+  | N/A                                                     |
> > > ++------------+-------+---------------------------------------------------------+
> > > +| Btrfs      |  L4   | N/A                                                     |
> > > ++------------+-------+---------------------------------------------------------+
> > > +| Ceph       |  L2   | N/A                                                     |
> > > ++------------+-------+---------------------------------------------------------+
> > > +| CIFS       |  L2-  | https://wiki.samba.org/index.php/Xfstesting-cifs        |
> > > ++------------+-------+---------------------------------------------------------+
> > > +| Ext2/3/4   |  L3+  | N/A                                                     |
> > 
> > What do the plus and minus mean?
> 
> Oh, I didn't explain them.
> 
> ("+" 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.)
> 
> Is that good to you?

<shrug> Insofar as those ratings are ongoing and fluid anyway, ok. :)

> > 
> > > ++------------+-------+---------------------------------------------------------+
> > > +| Exfat      |  L1+  | N/A                                                     |
> > > ++------------+-------+---------------------------------------------------------+
> > > +| f2fs       |  L3-  | N/A                                                     |
> > > ++------------+-------+---------------------------------------------------------+
> > > +| FUSE       |  L1   | N/A                                                     |
> > > ++------------+-------+---------------------------------------------------------+
> > > +| GFS2       |  L1   | N/A                                                     |
> > > ++------------+-------+---------------------------------------------------------+
> > > +| Glusterfs  |  L1   | N/A                                                     |
> > > ++------------+-------+---------------------------------------------------------+
> > > +| JFS        |  L1   | N/A                                                     |
> > > ++------------+-------+---------------------------------------------------------+
> > > +| NFS        |  L2+  | https://linux-nfs.org/wiki/index.php/Xfstests           |
> > > ++------------+-------+---------------------------------------------------------+
> > > +| ocfs2      |  L2-  | N/A                                                     |
> > > ++------------+-------+---------------------------------------------------------+
> > > +| overlay    |  L3   | N/A                                                     |
> > > ++------------+-------+---------------------------------------------------------+
> > > +| pvfs2      |  L1   | N/A                                                     |
> > > ++------------+-------+---------------------------------------------------------+
> > > +| Reiser4    |  L1   | Reiserfs has been removed, only left reiser4            |
> > > ++------------+-------+---------------------------------------------------------+
> > > +| tmpfs      |  L3-  | N/A                                                     |
> > > ++------------+-------+---------------------------------------------------------+
> > > +| ubifs      |  L1   | N/A                                                     |
> > > ++------------+-------+---------------------------------------------------------+
> > > +| udf        |  L1+  | N/A                                                     |
> > > ++------------+-------+---------------------------------------------------------+
> > > +| Virtiofs   |  L1   | N/A                                                     |
> > > ++------------+-------+---------------------------------------------------------+
> > > +| XFS        |  L4+  | N/A                                                     |
> > > ++------------+-------+---------------------------------------------------------+
> > > +| 9p         |  L1   | N/A                                                     |
> > > ++------------+-------+---------------------------------------------------------+
> > 
> > This roughly tracks with my observations over the years.
> 
> Some filesystems I never tried, likes "9p" and "ubifs" etc, I just found these names
> from common/rc.

Wasn't sandeen trying to make fstests work with fat at some point?
Well, it's not hard to add more to the table.

Looks good to me,
Acked-by: "Darrick J. Wong" <djwong@kernel.org>

--D

> If any fs list has any supplement to the fs name or the "comment", or would like to
> modify the "level", please feel free to tell me.
> 
> Thanks,
> Zorro
> 
> 
> 
> > 
> > --D
> > 
> > > +
> > >  _______________________
> > >  BUILDING THE FSQA SUITE
> > >  _______________________
> > > -- 
> > > 2.47.1
> > > 
> > > 
> > 
> 
> 

  reply	other threads:[~2025-02-28  6:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-27 20:05 [PATCH] README: add supported fs list Zorro Lang
2025-02-28  2:20 ` Darrick J. Wong
2025-02-28  5:16   ` Zorro Lang
2025-02-28  6:31     ` Darrick J. Wong [this message]
2025-02-28 13:55 ` David Sterba
2025-03-01 11:30   ` Zorro Lang

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=20250228063125.GC6225@frogsfrogsfrogs \
    --to=djwong@kernel.org \
    --cc=dsterba@suse.com \
    --cc=fstests@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=zlang@kernel.org \
    --cc=zlang@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox