From: Eryu Guan <guaneryu@gmail.com>
To: Deepa Dinamani <deepa.kernel@gmail.com>
Cc: fstests@vger.kernel.org, arnd@arndb.de, y2038@lists.linaro.org
Subject: Re: [PATCH] generic/402: fix for updated behavior of timestamp limits
Date: Mon, 22 Jul 2019 00:47:48 +0800 [thread overview]
Message-ID: <20190721164748.GK7943@desktop> (raw)
In-Reply-To: <20190719041231.26500-1-deepa.kernel@gmail.com>
On Thu, Jul 18, 2019 at 09:12:31PM -0700, Deepa Dinamani wrote:
> The mount behavior will not be altered because of the unsupported
> timestamps on the filesystems.
It'd be better to provide more details in the commit log, e.g. what
kind of mount behavior and what's the changes being made to the tests.
>
> Adjust the test accordingly.
>
> An updated series to be posted after the merge window is hosted at
> <https://github.com/deepa-hub/vfs/tree/limits>
>
> Signed-off-by: Deepa Dinamani <deepa.kernel@gmail.com>
Thanks for the update! But I'd like to wait for the kernel patches
merged into mainline first. Would you please send out a notification by
replying this thread then? Thanks a lot!
Eryu
> ---
> common/rc | 36 +++++++++---------
> tests/generic/402 | 87 ++++++++++++++++---------------------------
> tests/generic/402.out | 2 +-
> 3 files changed, 53 insertions(+), 72 deletions(-)
>
> diff --git a/common/rc b/common/rc
> index 25203bb4..39a2deb0 100644
> --- a/common/rc
> +++ b/common/rc
> @@ -1959,16 +1959,9 @@ _run_aiodio()
> return $status
> }
>
> -# this test requires y2038 sysfs switch and filesystem
> -# timestamp ranges support.
> -_require_y2038()
> +_require_timestamp_range()
> {
> local device=${1:-$TEST_DEV}
> - local sysfsdir=/proc/sys/fs/fs-timestamp-check-on
> -
> - if [ ! -e $sysfsdir ]; then
> - _notrun "no kernel support for y2038 sysfs switch"
> - fi
>
> local tsmin tsmax
> read tsmin tsmax <<<$(_filesystem_timestamp_range $device)
> @@ -1980,23 +1973,32 @@ _require_y2038()
> _filesystem_timestamp_range()
> {
> local device=${1:-$TEST_DEV}
> + u32max=$(((1<<32)-1))
> + s32min=-$((1<<31))
> + s32max=$(((1<<31)-1))
> + s64max=$(((1<<63)-1))
> + s64min=$((1<<63))
> +
> case $FSTYP in
> - ext4)
> + ext2)
> + echo "$s32min $s32max"
> + ;;
> + ext3|ext4)
> if [ $(dumpe2fs -h $device 2>/dev/null | grep "Inode size:" | cut -d: -f2) -gt 128 ]; then
> - echo "-2147483648 15032385535"
> + printf "%d %d\n" $s32min 0x37fffffff
> else
> - echo "-2147483648 2147483647"
> + echo "$s32min $s32max"
> fi
> ;;
>
> - xfs)
> - echo "-2147483648 2147483647"
> - ;;
> jfs)
> - echo "0 4294967295"
> + echo "0 $u32max"
> ;;
> - f2fs)
> - echo "-2147483648 2147483647"
> + xfs)
> + echo "$s32min $s32max"
> + ;;
> + btrfs)
> + echo "$s64min $s64max"
> ;;
> *)
> echo "-1 -1"
> diff --git a/tests/generic/402 b/tests/generic/402
> index f742fedd..dd136ec2 100755
> --- a/tests/generic/402
> +++ b/tests/generic/402
> @@ -4,15 +4,10 @@
> #
> # FS QA Test 402
> #
> -# Tests to verify policy for filesystem timestamps for
> -# supported ranges:
> -# 1. Verify filesystem rw mount according to sysctl
> -# timestamp_supported.
> -# 2. Verify timestamp clamping for timestamps beyond max
> -# timestamp supported.
> +# Test to verify filesystem timestamps for supported ranges.
> #
> -# Exit status 1: either or both tests above fail.
> -# Exit status 0: both the above tests pass.
> +# Exit status 1: test failed.
> +# Exit status 0: test passed.
> #
> seq=`basename $0`
> seqres=$RESULT_DIR/$seq
> @@ -49,47 +44,59 @@ check_stat()
> prev_timestamp="$timestamp;$timestamp"
> if [ $prev_timestamp != $stat_timestamp ]; then
> echo "$prev_timestamp != $stat_timestamp" | tee -a $seqres.full
> + return 1
> fi
> + return 0
> }
>
> run_test_individual()
> {
> + fail=0
> file=$1
> timestamp=$2
> update_time=$3
>
> # check if the time needs update
> if [ $update_time -eq 1 ]; then
> - echo "Updating file: $file to timestamp `date -d @$timestamp`" >> $seqres.full
> + echo "Updating file: $file to timestamp $timestamp" >> $seqres.full
> $XFS_IO_PROG -f -c "utimes $timestamp 0 $timestamp 0" $file
> if [ $? -ne 0 ]; then
> echo "Failed to update times on $file" | tee -a $seqres.full
> + fail=1
> fi
> fi
>
> - tsclamp=$(($timestamp>$tsmax?$tsmax:$timestamp))
> - echo "Checking file: $file Updated timestamp is `date -d @$tsclamp`" >> $seqres.full
> - check_stat $file $tsclamp
> + tsclamp=$((timestamp<tsmin?tsmin:timestamp>tsmax?tsmax:timestamp))
> + echo "Checking file: $file Updated timestamp is $tsclamp" >> $seqres.full
> + if ! check_stat $file $tsclamp; then
> + fail=1
> + fi
> + return $fail
> }
>
> run_test()
> {
> + fail=0
> update_time=$1
>
> n=1
>
> for TIME in "${TIMESTAMPS[@]}"; do
> - run_test_individual ${SCRATCH_MNT}/test_$n $TIME $update_time
> + if ! run_test_individual ${SCRATCH_MNT}/test_$n $TIME $update_time; then
> + fail=1
> + fi
> ((n++))
> done
> +
> + return $fail
> }
>
> _scratch_mkfs &>> $seqres.full 2>&1 || _fail "mkfs failed"
> -_require_y2038 $SCRATCH_DEV
> +_require_timestamp_range $SCRATCH_DEV
>
> read tsmin tsmax <<<$(_filesystem_timestamp_range $SCRATCH_DEV)
> -echo min supported timestamp $tsmin $(date --date=@$tsmin) >> $seqres.full
> -echo max supported timestamp $tsmax $(date --date=@$tsmax) >> $seqres.full
> +echo min supported timestamp $tsmin >> $seqres.full
> +echo max supported timestamp $tsmax >> $seqres.full
>
> # Test timestamps array
>
> @@ -97,45 +104,14 @@ declare -a TIMESTAMPS=(
> $tsmin
> 0
> $tsmax
> + $((tsmax/2))
> $((tsmax+1))
> - 4294967295
> - 8589934591
> - 34359738367
> )
>
> -# Max timestamp is hardcoded to Mon Jan 18 19:14:07 PST 2038
> -sys_tsmax=2147483647
> -echo "max timestamp that needs to be supported by fs for rw mount is" \
> - "$((sys_tsmax+1)) $(date --date=@$((sys_tsmax+1)))" >> $seqres.full
> -
> -read ts_check <<<$(cat /proc/sys/fs/fs-timestamp-check-on)
> -
> _scratch_mount
> result=$?
>
> -if [ $ts_check -ne 0 ]; then
> - echo "sysctl filesystem timestamp check is on" >> $seqres.full
> - # check for mount failure if the minimum requirement for max timestamp
> - # supported is not met.
> - if [ $sys_tsmax -ge $tsmax ]; then
> - if [ $result -eq 0 ]; then
> - echo "mount test failed" | tee -a $seqres.full
> - exit
> - fi
> - else
> - if [ $result -ne 0 ]; then
> - echo "failed to mount $SCRATCH_DEV" | tee -a $seqres.full
> - exit
> - fi
> - fi
> -else
> - # if sysctl switch is off then mount should succeed always.
> - echo "sysctl filesystem timestamp check is off" >> $seqres.full
> - if [ $result -ne 0 ]; then
> - echo "failed to mount $SCRATCH_DEV and timestamp check is off" >> $seqres.full
> - exit
> - fi
> -fi
> +status=0
>
> # Begin test case 1
> echo "In memory timestamps update test start" >> $seqres.full
> @@ -143,7 +119,9 @@ echo "In memory timestamps update test start" >> $seqres.full
> # update time on the file
> update_time=1
>
> -run_test $update_time
> +if ! run_test $update_time; then
> + status=1
> +fi
>
> echo "In memory timestamps update complete" >> $seqres.full
>
> @@ -162,12 +140,13 @@ update_time=0
> echo "On disk timestamps update test start" >> $seqres.full
>
> # Re-run test
> -run_test $update_time
> +if ! run_test $update_time; then
> + status=1
> +fi
>
> echo "On disk timestamps update test complete" >> $seqres.full
>
> -echo "y2038 inode timestamp tests completed successfully"
> +echo "inode timestamp tests completed status $status"
>
> # success, all done
> -status=0
> -exit
> +exit $status
> diff --git a/tests/generic/402.out b/tests/generic/402.out
> index 6c5b9308..4500e6c7 100644
> --- a/tests/generic/402.out
> +++ b/tests/generic/402.out
> @@ -1,2 +1,2 @@
> QA output created by 402
> -y2038 inode timestamp tests completed successfully
> +inode timestamp tests completed status 0
> --
> 2.17.1
>
next prev parent reply other threads:[~2019-07-21 16:47 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-19 4:12 [PATCH] generic/402: fix for updated behavior of timestamp limits Deepa Dinamani
2019-07-21 16:47 ` Eryu Guan [this message]
2019-10-02 22:06 ` Deepa Dinamani
2019-10-05 18:35 ` Eryu Guan
2019-10-23 22:17 ` Deepa Dinamani
2019-12-12 13:11 ` Amir Goldstein
2019-12-12 21:55 ` Deepa Dinamani
2019-12-18 20:21 ` Deepa Dinamani
2019-12-18 20:46 ` Amir Goldstein
2019-12-19 8:28 ` [Y2038] " Arnd Bergmann
2019-12-19 8:40 ` Greg KH
2019-12-19 11:29 ` Arnd Bergmann
2019-12-19 11:35 ` Greg KH
2019-12-19 15:48 ` [cip-dev] " Ben Hutchings
2019-12-19 15:48 ` Ben Hutchings
2019-12-19 20:35 ` [cip-dev] " Arnd Bergmann
2019-12-19 20:35 ` Arnd Bergmann
2019-12-19 12:09 ` Amir Goldstein
2019-12-20 22:45 ` Deepa Dinamani
2019-12-23 5:16 ` [PATCH] generic/402: Make timestamp range check conditional Deepa Dinamani
2019-12-23 6:36 ` Amir Goldstein
2019-12-24 1:15 ` Deepa Dinamani
2019-12-28 22:13 ` [PATCH v2] " Deepa Dinamani
2019-12-30 7:34 ` Amir Goldstein
2020-01-03 6:46 ` Deepa Dinamani
2020-01-03 9:58 ` Amir Goldstein
2020-01-08 8:09 ` Eryu Guan
2020-01-08 8:45 ` Amir Goldstein
2020-01-08 9:50 ` Eryu Guan
2020-01-17 9:09 ` Amir Goldstein
2020-01-17 18:23 ` Deepa Dinamani
2020-01-17 19:01 ` Deepa Dinamani
2020-01-19 0:57 ` [PATCH v3 1/1] " Deepa Dinamani
2020-01-19 9:19 ` Amir Goldstein
2020-02-01 9:14 ` Eryu Guan
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=20190721164748.GK7943@desktop \
--to=guaneryu@gmail.com \
--cc=arnd@arndb.de \
--cc=deepa.kernel@gmail.com \
--cc=fstests@vger.kernel.org \
--cc=y2038@lists.linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.