diff mbox

[6/7] generic/338: don't check fs after crashing it

Message ID 153067988515.28393.2889741998889842120.stgit@magnolia (mailing list archive)
State Accepted
Headers show

Commit Message

Darrick J. Wong July 4, 2018, 4:51 a.m. UTC 
From: Darrick J. Wong <darrick.wong@oracle.com>

This test tries to make the filesystem go down by setting up dm-error
and committing metadata updates.  Since the test doesn't remount the fs
after it goes down to recover the log, this can result in a dirty log
being presented to the post-test filesystem check if the filesystem is
xfs and quotas are enabled.

Since this is a regression test for a NULL pointer dereference in the
kernel after the fs goes down, simply skip the post-test fsck.

Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com>
---
 tests/generic/338 |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)



--
To unsubscribe from this list: send the line "unsubscribe linux-xfs" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
diff mbox

Patch

diff --git a/tests/generic/338 b/tests/generic/338
index 6d701e83..81122e2d 100755
--- a/tests/generic/338
+++ b/tests/generic/338
@@ -36,7 +36,7 @@  rm -f $seqres.full
 # real QA test starts here
 _supported_fs generic
 _supported_os Linux
-_require_scratch
+_require_scratch_nocheck # fs went down with a dirty log, don't check it
 _require_dm_target error
 # If SCRATCH_DEV is not a valid block device, FSTYP cannot be mkfs'ed either
 _require_block_device $SCRATCH_DEV