From: Eryu Guan <eguan@redhat.com>
To: Zorro Lang <zlang@redhat.com>
Cc: fstests@vger.kernel.org, sandeen@redhat.com, cem@redhat.com
Subject: Re: [PATCH v4 1/2] common/rc: add functions to check or write objects under /sys/fs/$FSTYP
Date: Tue, 21 Jun 2016 14:54:34 +0800 [thread overview]
Message-ID: <20160621065434.GS5140@eguan.usersys.redhat.com> (raw)
In-Reply-To: <1466429073-10124-1-git-send-email-zlang@redhat.com>
On Mon, Jun 20, 2016 at 09:24:32PM +0800, Zorro Lang wrote:
> 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/${FSTYP}.
> 2. write a file in /sys/fs/${FSTYP}.
>
> For common use, these functions can be used by other filesystems.
>
> Signed-off-by: Zorro Lang <zlang@redhat.com>
> ---
>
> Hi,
>
> V4 did below changes:
> 1) function name from *_fs_sys_fs to *_fs_sysfs
> 2) use $UMOUNT_PROG to instead of umount
> 3) use _short_dev
> 4) add comments for new functions
> 5) other little changes
>
> Thanks,
> Zorro
>
> common/rc | 42 ++++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 42 insertions(+)
>
> diff --git a/common/rc b/common/rc
> index 51092a0..88c3777 100644
> --- a/common/rc
> +++ b/common/rc
> @@ -3556,6 +3556,48 @@ run_fsx()
> fi
> }
>
> +# Test for the existence of a sysfs entry at /sys/fs/$FSTYP/$DEV/$ENTRY
> +_require_fs_sysfs()
> +{
> + local dev=$1
> + local entry=$2
> + local tmp_mnt=`mktemp -d`
> +
> + if [ ! -b "$dev" -o -z "$entry" ];then
> + _fail "Usage: _require_fs_sysfs <device> <sysfs_path>"
> + fi
Mixed tab and space in above line.
> +
> + local dname=$(_short_dev $dev)
> + _mount -t $FSTYP `_common_dev_mount_options` $dev $tmp_mnt
> + if [ $? -ne 0 ];then
> + rm -f $tmp_mnt
> + _fail "_require_fs_sysfs: could not mount, mkfs first in your test?"
I'd like to see which device failed to mount in error message.
> + elif [ ! -e /sys/fs/${FSTYP}/${dname}/${entry} ];then
> + $UMOUNT_PROG $tmp_mnt
> + rm -f $tmp_mnt
> + _notrun "/sys/fs/${FSTYP}/${dname}/${entry}: No such file or directory"
> + fi
> + $UMOUNT_PROG $tmp_mnt
> + rm -rf $tmp_mnt
> +}
> +
> +# Write "content" into /sys/fs/$FSTYP/$DEV/$ENTRY
> +_set_fs_sysfs_param()
I think we can have a _get_fs_sysfs_param() helper to ensure the value
is correct.
Maybe naming them as _set|get_fs_sysfs_attr()?
Thanks,
Eryu
> +{
> + local dev=$1
> + shift
> + local entry=$1
> + shift
> + local content="$*"
> +
> + if [ ! -b "$dev" -o -z "$entry" -o -z "$content" ];then
> + _fail "Usage: _set_fs_sysfs_param <mounted_device> <entry> <content>"
> + fi
> +
> + local dname=$(_short_dev $dev)
> + echo "$content" > /sys/fs/${FSTYP}/${dname}/${entry}
> +}
> +
> init_rc
>
> ################################################################################
> --
> 2.5.5
>
prev parent reply other threads:[~2016-06-21 6:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-20 13:24 [PATCH v4 1/2] common/rc: add functions to check or write objects under /sys/fs/$FSTYP Zorro Lang
2016-06-20 13:24 ` [PATCH v4 2/2] xfs/006: new case to test xfs fail_at_unmount error handling Zorro Lang
2016-06-21 7:08 ` Eryu Guan
2016-06-22 0:00 ` Dave Chinner
2016-06-22 1:42 ` Zirong Lang
2016-06-22 3:04 ` Dave Chinner
2016-06-22 3:15 ` Zirong Lang
2016-06-22 3:04 ` Eric Sandeen
2016-06-22 3:17 ` Zirong Lang
2016-06-21 6:54 ` Eryu Guan [this message]
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=20160621065434.GS5140@eguan.usersys.redhat.com \
--to=eguan@redhat.com \
--cc=cem@redhat.com \
--cc=fstests@vger.kernel.org \
--cc=sandeen@redhat.com \
--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