From 961956168b7b45e884d28aec832d9edfbe79d5d2 Mon Sep 17 00:00:00 2001 From: "Darrick J. Wong" Date: Wed, 28 Sep 2016 19:28:34 -0700 Subject: [PATCH] xfs/130: don't modify files after failed mount In xfs/130, we try to mount a filesystem with the expectation that it will fail. Therefore, it is inappropriate to try to write to the mountpoint, since it could otherwise be writable. Signed-off-by: Darrick J. Wong Reviewed-by: Dave Chinner Signed-off-by: Eryu Guan --- tests/xfs/130 | 9 +++------ tests/xfs/130.out | 1 - 2 files changed, 3 insertions(+), 7 deletions(-) diff --git a/tests/xfs/130 b/tests/xfs/130 index 554d0789..48f6a846 100755 --- a/tests/xfs/130 +++ b/tests/xfs/130 @@ -79,12 +79,9 @@ seq 0 $((agcount - 1)) | while read ag; do done echo "+ mount image" -_scratch_mount - -echo "+ reflink more" -_cp_reflink "${SCRATCH_MNT}/file1" "${SCRATCH_MNT}/file4" 2> /dev/null && \ - _fail "should not be able to reflink with busted refcount btree" -umount "${SCRATCH_MNT}" +_scratch_mount >> $seqres.full 2>&1 && \ + echo "Should not be able to mount with broken refcountbt." +_scratch_unmount >> $seqres.full 2>&1 echo "+ repair fs" _disable_dmesg_check diff --git a/tests/xfs/130.out b/tests/xfs/130.out index 58d153b4..a0eab987 100644 --- a/tests/xfs/130.out +++ b/tests/xfs/130.out @@ -5,7 +5,6 @@ QA output created by 130 + check fs + corrupt image + mount image -+ reflink more + repair fs + mount image (2) + chattr -R -i -- 2.39.5