fstests: _require_dm_target should not always skip DAX capable devices
authorDave Chinner <dchinner@redhat.com>
Wed, 27 Oct 2021 01:38:42 +0000 (12:38 +1100)
committerEryu Guan <guaneryu@gmail.com>
Sun, 31 Oct 2021 14:18:52 +0000 (22:18 +0800)
commit5c4de305a3a75b7db982821330a51e775a3678c4
tree54e0b6c0a09e8320456da6c02bfa8bcaf96f2e71
parent7ca10f2b05e57d9816af51da04c336284691ae79
fstests: _require_dm_target should not always skip DAX capable devices

Recent changes have turned off all dm-error, dm-thin and dm-flakey
tests on pmem devices even when we are not explicitly testing DAX.
This is a regression resulting in a large number of log recovery
tests no longer running on my pmem-based test VMs. I added the "-o
dax=never" mount options to these test configs, only to find it
still would not run the dm tests even though the filesystem will
never use DAX.

Fix this so that the dm target DAX test explicitly ignores the
the block device DAX capability when the filesystem is mounted with
dax=never and hence we can use all the dm targets when the tests are
being run with FSDAX disabled.

Signed-off-by: Dave Chinner <dchinner@redhat.com>
Reviewed-by: Darrick J. Wong <djwong@kernel.org>
Reviewed-by: Zorro Lang <zlang@redhat.com>
Signed-off-by: Eryu Guan <guaneryu@gmail.com>
common/rc