From: Zorro Lang <zlang@redhat.com>
To: fstests@vger.kernel.org
Cc: cem@redhat.com, Zorro Lang <zlang@redhat.com>
Subject: [PATCH 1/2] common/rc: add functions to check or write objects under /sys/fs
Date: Fri, 27 May 2016 23:21:21 +0800 [thread overview]
Message-ID: <1464362482-7704-1-git-send-email-zlang@redhat.com> (raw)
XFS add more configurations in /sys/fs/xfs recently. For use
them, this patch add some common functions for:
1. "require" a file/dir in /sys/fs.
2. write a file in /sys/fs.
For common use, these functions can be used by other filesystems.
Signed-off-by: Zorro Lang <zlang@redhat.com>
---
common/rc | 81 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
1 file changed, 81 insertions(+)
diff --git a/common/rc b/common/rc
index 51092a0..9935f08 100644
--- a/common/rc
+++ b/common/rc
@@ -3556,6 +3556,87 @@ run_fsx()
fi
}
+_require_sys_fs()
+{
+ local dev=$1
+ local target=$2
+ local dname=""
+
+ if [ ! -b "$dev" -o -z "$target" ];then
+ echo "Usage: _require_sys_fs <device> <target_need_exist>"
+ exit 1
+ fi
+
+ dname=$(basename $(readlink -f $dev))
+ _mkfs_dev $dev > /dev/null 2>&1
+ _mount -t $FSTYP `_common_dev_mount_options` $dev $SCRATCH_MNT
+ if [ ! -e /sys/fs/${FSTYP}/${dname}/$target ];then
+ umount $SCRATCH_MNT
+ _notrun "/sys/fs/${FSTYP}/${dname}/$target: No such file or directory"
+ fi
+ umount $SCRATCH_MNT
+}
+
+_require_scratch_sys_fs()
+{
+ local target=$1
+ local dname=""
+
+ if [ ! -b "$SCRATCH_DEV" -o -z "$target" ];then
+ echo "Usage: _require_scratch_sys_fs <target_need_exist>"
+ exit 1
+ fi
+
+ dname=$(basename $(readlink -f $SCRATCH_DEV))
+ _scratch_mkfs > /dev/null 2>&1
+ _scratch_mount
+ if [ ! -e /sys/fs/${FSTYP}/${dname}/$target ];then
+ _scratch_unmount
+ _notrun "/sys/fs/${FSTYP}/${dname}/$target: No such file or directory"
+ fi
+ _scratch_unmount
+}
+
+_set_sys_fs_param()
+{
+ local dev=$1
+ shift
+ local target=$1
+ shift
+ local content="$*"
+
+ if [ ! -b "$dev" -o -z "$target" -o -z "$content" ];then
+ echo "Usage: _set_sys_fs_param <mounted_device> <target> <content>"
+ exit 1
+ fi
+ local dname=$(basename $(readlink -f $dev))
+ echo "$content" > /sys/fs/${FSTYP}/${dname}/$target
+}
+
+_enable_xfs_fail_at_unmount()
+{
+ local dev=$1
+
+ if [ ! -b "$dev" -o "$FSTYP" != "xfs" ];then
+ echo "Usage: _enable_xfs_fail_at_unmount <mounted_XFS_device>"
+ exit 1
+ fi
+
+ _set_sys_fs_param $dev error/fail_at_unmount 1
+}
+
+_disable_xfs_fail_at_unmount()
+{
+ local dev=$1
+
+ if [ ! -b "$dev" -o "$FSTYP" != "xfs" ];then
+ echo "Usage: _enable_xfs_fail_at_unmount <mounted_XFS_device>"
+ exit 1
+ fi
+
+ _set_sys_fs_param $dev error/fail_at_unmount 0
+}
+
init_rc
################################################################################
--
2.5.5
next reply other threads:[~2016-05-27 15:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-27 15:21 Zorro Lang [this message]
2016-05-27 15:21 ` [PATCH 2/2] xfs/006: new case to test xfs fail_at_unmount error handling Zorro Lang
2016-05-27 18:26 ` Eric Sandeen
2016-05-28 16:56 ` Zorro Lang
2016-05-27 18:05 ` [PATCH 1/2] common/rc: add functions to check or write objects under /sys/fs Eric Sandeen
2016-05-27 18:27 ` Eric Sandeen
2016-05-28 16:42 ` Zorro Lang
2016-05-28 17:54 ` Eric Sandeen
2016-05-28 16:36 ` Zorro Lang
2016-05-28 18:06 ` Eric Sandeen
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=1464362482-7704-1-git-send-email-zlang@redhat.com \
--to=zlang@redhat.com \
--cc=cem@redhat.com \
--cc=fstests@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