From: Eryu Guan <eguan@redhat.com>
To: Amir Goldstein <amir73il@gmail.com>
Cc: Miklos Szeredi <miklos@szeredi.hu>,
linux-unionfs@vger.kernel.org, fstests@vger.kernel.org
Subject: Re: [PATCH 1/2] fstest: add helper _require_fs_feature
Date: Thu, 13 Jul 2017 20:41:27 +0800 [thread overview]
Message-ID: <20170713124127.GG2478@eguan.usersys.redhat.com> (raw)
In-Reply-To: <1499852605-27759-2-git-send-email-amir73il@gmail.com>
On Wed, Jul 12, 2017 at 12:43:24PM +0300, Amir Goldstein wrote:
> The helper is used to test if a specific filesystem feature can
> be enabled. Currently only implemented testing overlayfs features.
>
> Overalyfs features (e.g. redirect_dir, index) are configurable from
> Kconfig (the build default), by module parameter (the system default)
> and per mount using the mount option ${feature}=[on|off].
>
> The helper is going to be used by overlay tests, which depend
> on the inodes index feature.
>
> Signed-off-by: Amir Goldstein <amir73il@gmail.com>
> ---
> common/rc | 48 ++++++++++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 48 insertions(+)
>
> diff --git a/common/rc b/common/rc
> index b505365..260b48d 100644
> --- a/common/rc
> +++ b/common/rc
> @@ -3626,6 +3626,54 @@ _get_fs_sysfs_attr()
> cat /sys/fs/${FSTYP}/${dname}/${attr}
> }
>
> +# Print the value of a filesystem module parameter
> +# at /sys/module/$FSTYP/parameters/$PARAM
> +#
> +# Usage example (FSTYP=overlay):
> +# _get_fs_module_param index
> +_get_fs_module_param()
> +{
> + cat /sys/module/${FSTYP}/parameters/${1} 2>/dev/null
> +}
> +
> +# Generic test for specific filesystem feature.
> +# Currently only implemented to test overlayfs features.
> +_require_fs_feature()
I'd think if it should be renamed to _require_scratch_feature, because
it assumes $SCRATCH_DEV is present, and it reminds people it's using
SCRATCH_DEV with "scratch" in the name.
Otherwise looks good to me, it has detailed explanations, thanks a lot!
> +{
> + local feature=$1
> +
> + case "$FSTYP" in
> + overlay)
> + # overalyfs features (e.g. redirect_dir, index) are
> + # configurable from Kconfig (the build default), by module
> + # parameter (the system default) and per mount by mount
> + # option ${feature}=[on|off].
I'll fix the indention here, like
case "$FSTYP" in
overlay)
...
;;
*)
;;
esac
Thanks,
Eryu
> + #
> + # If the module parameter does not exist then there is no
> + # point in checking the mount option.
> + local default=`_get_fs_module_param ${feature}`
> + [ "$default" = Y ] || [ "$default" = N ] || \
> + _notrun "feature '${feature}' not supported by ${FSTYP}"
> +
> + _scratch_mkfs > /dev/null 2>&1
> + _scratch_mount -o ${feature}=on || \
> + _notrun "${FSTYP} feature '${feature}' cannot be enabled on ${SCRATCH_DEV}"
> + # Check options to be sure. For example, Overlayfs will fallback to
> + # index=off if underlying fs does not support file handles.
> + # Overlayfs only displays mount option if it differs from the default.
> + # Overlayfs may enable the feature, but fallback to read-only mount.
> + ((( [ "$default" = N ] && _fs_options $SCRATCH_DEV | grep -q "${feature}=on" ) || \
> + ( [ "$default" = Y ] && ! _fs_options $SCRATCH_DEV | grep -q "${feature}=off" )) && \
> + touch $SCRATCH_MNT/foo 2>/dev/null ) || \
> + _notrun "${FSTYP} feature '${feature}' cannot be enabled on ${SCRATCH_DEV}"
> + _scratch_unmount
> + ;;
> + *)
> + _fail "Test for feature '${feature}' of ${FSTYP} is not implemented"
> + ;;
> + esac
> +}
> +
>
> init_rc
>
> --
> 2.7.4
>
next prev parent reply other threads:[~2017-07-13 12:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-12 9:43 [PATCH 0/2] Require overlay index feature for hardlink tests Amir Goldstein
2017-07-12 9:43 ` [PATCH 1/2] fstest: add helper _require_fs_feature Amir Goldstein
2017-07-13 12:41 ` Eryu Guan [this message]
2017-07-13 13:10 ` Amir Goldstein
2017-07-14 2:54 ` Eryu Guan
2017-07-12 9:43 ` [PATCH 2/2] overlay: enable the index feature for overlay/hardlink tests Amir Goldstein
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=20170713124127.GG2478@eguan.usersys.redhat.com \
--to=eguan@redhat.com \
--cc=amir73il@gmail.com \
--cc=fstests@vger.kernel.org \
--cc=linux-unionfs@vger.kernel.org \
--cc=miklos@szeredi.hu \
/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