Files
apfstests/tests/generic/042
T
Zhihao Cheng b7cecbea22 fstests: Add path $here before src/<file>
Calling src/<file> without path '$here' may cause the problem that
the file cannot be found.

For example, Running generic/192 with overlayfs(Let ubifs as base
fs) yields the following output:

  generic/192 - output mismatch
     QA output created by 192
     sleep for 5 seconds
     test
    +./common/rc: line 316: src/t_dir_type: No such file or directory
     delta1 is in range
     delta2 is in range
    ...

When the use case fails, the call stack in generic/192 is:

  local unknowns=$(src/t_dir_type $dir u | wc -l)	common/rc
  _supports_filetype					common/rc
  _overlay_mount					common/overlay
  _overlay_test_mount					common/overlay
  _test_mount						common/rc
  _test_cycle_mount					generic/192

Before _test_cycle_mount() being invoked, generic/192 executed 'cd
/' to change work dir from 'xfstests-dev' to '/', so src/t_dir_type
was not found.

[Eryu: some tests run src/<file> as regular user, don't add $here
prefix in such case, as a regular user may have no search permission
on $here]

Signed-off-by: Zhihao Cheng <chengzhihao1@huawei.com>
Reviewed-by: Eryu Guan <guaneryu@gmail.com>
Signed-off-by: Eryu Guan <guaneryu@gmail.com>
2019-10-23 23:12:42 +08:00

94 lines
2.2 KiB
Bash
Executable File

#! /bin/bash
# SPDX-License-Identifier: GPL-2.0
# Copyright (c) 2014 Red Hat, Inc. All Rights Reserved.
#
# FS QA Test No. 042
#
# Test stale data exposure via writeback using various file allocation
# modification commands. The presumption is that such commands result in partial
# writeback and can convert a delayed allocation extent, that might be larger
# than the ranged affected by fallocate, to a normal extent. If the fs happens
# to crash sometime between when the extent modification is logged and writeback
# occurs for dirty pages within the extent but outside of the fallocated range,
# stale data exposure can occur.
#
seq=`basename $0`
seqres=$RESULT_DIR/$seq
echo "QA output created by $seq"
here=`pwd`
tmp=/tmp/$$
status=1 # failure is the default!
trap "_cleanup; exit \$status" 0 1 2 3 15
_cleanup()
{
cd /
rm -f $tmp.*
}
# get standard environment, filters and checks
. ./common/rc
. ./common/filter
. ./common/punch
# real QA test starts here
rm -f $seqres.full
_crashtest()
{
cmd=$1
img=$SCRATCH_MNT/$seq.img
mnt=$SCRATCH_MNT/$seq.mnt
file=$mnt/file
# Create an fs on a small, initialized image. The pattern is written to
# the image to detect stale data exposure.
$XFS_IO_PROG -f -c "truncate 0" -c "pwrite -S 0xCD 0 25M" $img \
>> $seqres.full 2>&1
_mkfs_dev $img >> $seqres.full 2>&1
mkdir -p $mnt
_mount $img $mnt
echo $cmd
# write, run the test command and shutdown the fs
$XFS_IO_PROG -f -c "pwrite -S 1 0 64k" -c "$cmd 60k 4k" $file | \
_filter_xfs_io
$here/src/godown -f $mnt
$UMOUNT_PROG $mnt
_mount $img $mnt
# We should /never/ see 0xCD in the file, because we wrote that pattern
# to the filesystem image to expose stale data.
if hexdump -v -e '/1 "%02X "' $file | grep -q "CD"; then
echo "Saw stale data!!!"
hexdump $file
fi
$UMOUNT_PROG $mnt
}
# Modify as appropriate.
_supported_fs generic
_supported_os Linux
_require_scratch
_require_scratch_shutdown
_require_xfs_io_command "falloc"
_require_xfs_io_command "fpunch"
_require_xfs_io_command "fzero"
_scratch_mkfs >/dev/null 2>&1
_require_local_device $SCRATCH_DEV
_require_metadata_journaling $SCRATCH_DEV
_scratch_mount
_crashtest "falloc -k"
_crashtest "fpunch"
_crashtest "fzero -k"
status=0
exit