Files
apfstests/tests/generic/451
T
Zorro Lang 53600ec6d3 generic: test data integrity with mixed buffer read and aio dio write
When mixing buffered reads and asynchronous direct writes, it is
possible to end up with the situation where we have stale data in
the page cache while the new data is already written to disk.

This issue should be fixed by patch titled:

fs: Fix page cache inconsistency when mixing buffered and AIO DIO

Signed-off-by: Zorro Lang <zlang@redhat.com>
Reviewed-by: Eryu Guan <eguan@redhat.com>
Signed-off-by: Eryu Guan <eguan@redhat.com>
2017-08-28 18:08:22 +08:00

91 lines
2.4 KiB
Bash
Executable File

#! /bin/bash
# FS QA Test No. 451
#
# Test data integrity when mixing buffered reads and asynchronous
# direct writes a file.
#
#-----------------------------------------------------------------------
# Copyright (c) 2017 Red Hat Inc. All Rights Reserved.
#
# This program is free software; you can redistribute it and/or
# modify it under the terms of the GNU General Public License as
# published by the Free Software Foundation.
#
# This program is distributed in the hope that it would be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
# GNU General Public License for more details.
#
# You should have received a copy of the GNU General Public License
# along with this program; if not, write the Free Software Foundation,
# Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA
#-----------------------------------------------------------------------
#
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
# remove previous $seqres.full before test
rm -f $seqres.full
# real QA test starts here
_supported_fs generic
_supported_os Linux
_require_test
_require_test_program "feature"
_require_aiodio aio-dio-cycle-write
_require_command "$TIMEOUT_PROG" timeout
TESTFILE=$TEST_DIR/tst-aio-dio-cycle-write.$seq
FSIZE=655360 # bytes
# More read processes can help to reproduce the bug easier, so run
# 2 ~ 20 readers according to the number of CPUs
nr_cpu=`$here/src/feature -o`
loops=$((nr_cpu / 2))
if [ $loops -lt 2 ]; then
loops=2
elif [ $loops -gt 20 ]; then
loops=20
fi
keep_reading=$tmp.reading
touch $keep_reading
# buffered reads the file frequently
for ((i=0; i<loops; i++)); do
while [ -e $keep_reading ]; do
$XFS_IO_PROG -f -c "pread 0 $FSIZE" $TESTFILE >/dev/null 2>&1
done &
reader_pid="$reader_pid $!"
done
# start an aio writer, which does writing loops internally and check
# data integrality.
# For reproduce the original bug, keep testing about 30s will be better,
# So let the AIO_TEST run as many loops as it can, then kill it in 30s.
$TIMEOUT_PROG -s TERM 30s $AIO_TEST -c 999999 -b $FSIZE $TESTFILE >/dev/null
# Remove $keep_reading file to stop the reader cycle
rm -f $keep_reading
wait $reader_pid
echo "Silence is golden"
status=0
exit