FS/XFS testing framework
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Zorro Lang <zlang@kernel.org>
Cc: fstests@vger.kernel.org, "Theodore Ts'o" <tytso@mit.edu>,
	linux-ext4@vger.kernel.org
Subject: [PATCH 6/8] generic/745: rework support fs checking
Date: Sun, 23 Jun 2024 14:10:35 +0200	[thread overview]
Message-ID: <20240623121103.974270-7-hch@lst.de> (raw)
In-Reply-To: <20240623121103.974270-1-hch@lst.de>

To prepare for deprecating _supported_fs use a case statement and
_notrun.

Signed-off-by: Christoph Hellwig <hch@lst.de>
---
 tests/generic/745 | 15 ++++++++++-----
 1 file changed, 10 insertions(+), 5 deletions(-)

diff --git a/tests/generic/745 b/tests/generic/745
index 0f47f9c69..bed43578a 100755
--- a/tests/generic/745
+++ b/tests/generic/745
@@ -27,16 +27,21 @@ _cleanup()
 . ./common/dmflakey
 . ./common/attr
 
-# real QA test starts here
+_require_scratch
+_require_dm_target flakey
+_require_attrs
 
 # We create a lot of xattrs for a single file. Only btrfs and xfs are currently
 # able to store such a large mount of xattrs per file, other filesystems such
 # as ext3/4 and f2fs for example, fail with ENOSPC even if we attempt to add
 # less than 1000 xattrs with very small values.
-_supported_fs btrfs xfs
-_require_scratch
-_require_dm_target flakey
-_require_attrs
+case "$FSTYP" in
+btrfs|xfs)
+	;;
+*)
+	_notrun "Requires support for > 1000 xattrs"
+	;;
+esac
 
 _scratch_mkfs >> $seqres.full 2>&1
 _require_metadata_journaling $SCRATCH_DEV
-- 
2.43.0


  parent reply	other threads:[~2024-06-23 12:11 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-23 12:10 mostly remove _supported_fs Christoph Hellwig
2024-06-23 12:10 ` [PATCH 1/8] remove support for ext4dev Christoph Hellwig
2024-06-23 12:10 ` [PATCH 2/8] generic/740: clean up handling of mkfs options Christoph Hellwig
2024-06-23 12:10 ` [PATCH 3/8] generic/740: pass the --quick option to mkfs.ntfs Christoph Hellwig
2024-06-23 12:10 ` [PATCH 4/8] generic/740: skip jffs2 as foreign fs earlier Christoph Hellwig
2024-06-23 12:10 ` [PATCH 5/8] generic/740: enable by default Christoph Hellwig
2024-06-24 16:16   ` Darrick J. Wong
2024-06-25  3:50     ` Theodore Ts'o
2024-06-25  6:00       ` Christoph Hellwig
2024-06-25 20:05         ` Theodore Ts'o
2024-06-26  4:01           ` Christoph Hellwig
2024-06-23 12:10 ` Christoph Hellwig [this message]
2024-06-23 12:10 ` [PATCH 7/8] generic/746: clean up fs support Christoph Hellwig
2024-06-23 12:10 ` [PATCH 8/8] remove spurious _supported_fs calls Christoph Hellwig
2024-06-24  2:17 ` mostly remove _supported_fs David Disseldorp
2024-06-24 16:17 ` Darrick J. Wong
2024-07-10  6:16 ` Christoph Hellwig
2024-07-11 13:16   ` 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=20240623121103.974270-7-hch@lst.de \
    --to=hch@lst.de \
    --cc=fstests@vger.kernel.org \
    --cc=linux-ext4@vger.kernel.org \
    --cc=tytso@mit.edu \
    --cc=zlang@kernel.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