From: Darrick J. Wong Date: Wed, 4 Jul 2018 04:51:25 +0000 (-0700) Subject: generic/338: don't check fs after crashing it X-Git-Tag: v2022.05.01~1453 X-Git-Url: https://www.infradead.org/git/?a=commitdiff_plain;h=26cfcac295064409f83e7eb0102edbedaea0cd07;p=users%2Fhch%2Fxfstests-dev.git generic/338: don't check fs after crashing it 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 Reviewed-by: Eryu Guan Signed-off-by: Eryu Guan --- diff --git a/tests/generic/338 b/tests/generic/338 index 6d701e833..81122e2d3 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