From: Eric Sandeen <sandeen@redhat.com>
To: linux-xfs@vger.kernel.org, fstests@vger.kernel.org
Subject: [PATCH V3] mkfs.xfs: test that shipped config files work properly
Date: Mon, 5 Jun 2023 16:14:34 -0500 [thread overview]
Message-ID: <1685999674-8626-1-git-send-email-sandeen@redhat.com> (raw)
In-Reply-To: <1685999495-7998-1-git-send-email-sandeen@redhat.com>
Sanity check the shipped mkfs.xfs config files by using
them to format the scratch device.
Signed-off-by: Eric Sandeen <sandeen@redhat.com>
---
tests/xfs/569 | 32 ++++++++++++++++++++++++++++++++
tests/xfs/569.out | 2 ++
2 files changed, 34 insertions(+)
create mode 100755 tests/xfs/569
create mode 100644 tests/xfs/569.out
diff --git a/tests/xfs/569 b/tests/xfs/569
new file mode 100755
index 0000000..e890270
--- /dev/null
+++ b/tests/xfs/569
@@ -0,0 +1,32 @@
+#! /bin/bash
+# SPDX-License-Identifier: GPL-2.0
+# Copyright (c) 2023 Red Hat, Inc. All Rights Reserved.
+#
+# FS QA Test 569
+#
+# Check for any installed example mkfs config files and validate that
+# mkfs.xfs can properly use them.
+#
+. ./common/preamble
+_begin_fstest mkfs
+
+# real QA test starts here
+
+# Modify as appropriate.
+_supported_fs xfs
+_require_scratch
+
+ls /usr/share/xfsprogs/mkfs/*.conf &>/dev/null || \
+ _notrun "No mkfs.xfs config files installed"
+
+# We only fail if mkfs.xfs fails outright, ignoring warnings etc
+echo "Silence is golden"
+
+for CONFIG in /usr/share/xfsprogs/mkfs/*.conf; do
+ $MKFS_XFS_PROG -c options=$CONFIG -f $SCRATCH_DEV &>>$seqres.full || \
+ echo "mkfs.xfs config file $CONFIG failed"
+done
+
+# success, all done
+status=0
+exit
diff --git a/tests/xfs/569.out b/tests/xfs/569.out
new file mode 100644
index 0000000..c7aaf10
--- /dev/null
+++ b/tests/xfs/569.out
@@ -0,0 +1,2 @@
+QA output created by 569
+Silence is golden
--
1.8.3.1
next prev parent reply other threads:[~2023-06-05 21:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-05 21:11 [PATCH V2] mkfs.xfs: test that shipped config files work properly Eric Sandeen
2023-06-05 21:14 ` Eric Sandeen [this message]
2023-06-05 22:06 ` [PATCH V3] " Darrick J. Wong
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=1685999674-8626-1-git-send-email-sandeen@redhat.com \
--to=sandeen@redhat.com \
--cc=fstests@vger.kernel.org \
--cc=linux-xfs@vger.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