Files
apfstests/tests/generic/360
T
Eric Sandeen 2b0162607d fstests: use _require_symlinks on all necessary tests
Consistently use _require_symlinks on all generic tests which
create a symlink when they run.

Signed-off-by: Eric Sandeen <sandeen@redhat.com>
Reviewed-by: Zorro Lang <zlang@redhat.com>
Signed-off-by: Eryu Guan <guaneryu@gmail.com>
2020-04-20 00:42:11 +08:00

52 lines
1023 B
Bash
Executable File

#! /bin/bash
# SPDX-License-Identifier: GPL-2.0
# Copyright (c) 2016 Red Hat Inc. All Rights Reserved.
#
# FS QA Test 360
#
# Test symlink to very long path, check symlink file contains correct path.
#
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
rm -f $seqres.full
# real QA test starts here
_supported_fs generic
_supported_os Linux
_require_test
_require_symlinks
linkfile=$TEST_DIR/$seq.symlink
rm -f $linkfile
FNAME=$(perl -e 'print "a"x254')
# Create a symlink points to a very long path, so that the path could not be
# hold in inode
ln -s $FNAME/$FNAME/$FNAME/$FNAME $linkfile
# Check symlink contains the correct path.
# 1023 chars are a bit long for golden image output, compute the md5 checksum
readlink $linkfile | md5sum
# success, all done
status=0
exit