Generally these tests are not restricted to one device or the other;
testing the test device will suffice to determine the capability
but it doesn't need to be named that way.
Signed-off-by: Eric Sandeen <sandeen@redhat.com>
Reviewed-by: Zorro Lang <zlang@redhat.com>
Signed-off-by: Eryu Guan <guaneryu@gmail.com>
"$@" >> $seqres.full 2>&1 || _fail "failed: '$@'"
}
"$@" >> $seqres.full 2>&1 || _fail "failed: '$@'"
}
-_require_test_symlinks()
{
local target=`mktemp -p $TEST_DIR`
local link=`mktemp -p $TEST_DIR -u`
{
local target=`mktemp -p $TEST_DIR`
local link=`mktemp -p $TEST_DIR -u`
# real QA test starts here
_supported_fs generic
_require_test
# real QA test starts here
_supported_fs generic
_require_test
_require_test
_require_renameat2
_require_test
_require_renameat2
# real QA test starts here
# real QA test starts here
_require_test
_require_renameat2 noreplace
_require_test
_require_renameat2 noreplace
# real QA test starts here
# real QA test starts here
_require_test
_require_renameat2 exchange
_require_test
_require_renameat2 exchange
# real QA test starts here
# real QA test starts here
# Modify as appropriate.
_supported_fs generic
_supported_os Linux
# Modify as appropriate.
_supported_fs generic
_supported_os Linux
_require_test
_require_scratch
_require_loop
_require_test
_require_scratch
_require_loop
_require_test
_require_renameat2 whiteout
_require_test
_require_renameat2 whiteout
# real QA test starts here
# real QA test starts here