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 <darrick.wong@oracle.com>
Reviewed-by: Eryu Guan <guaneryu@gmail.com>
Signed-off-by: Eryu Guan <guaneryu@gmail.com>
This commit is contained in:
Darrick J. Wong
2018-07-03 21:51:25 -07:00
committed by Eryu Guan
parent b3cf8b7233
commit 26cfcac295
+1 -1
View File
@@ -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