Handle xfstests results with and without direct I/O

Use the same check as we do in Makefile.kernelcompat
(look for copy_page_to_iter_nofault in the kernel uio.h
header file) to determine if we should use the no DIO
version of expected xfstests results.

Signed-off-by: Chris Kirby <ckirby@versity.com>
This commit is contained in:
Chris Kirby
2026-07-19 17:14:24 -05:00
parent 0a77a233fd
commit eeb6bf6b2b
4 changed files with 889 additions and 13 deletions
+5
View File
@@ -231,6 +231,11 @@ t_filter_dmesg()
# lockdep or kasan warnings can cause this
re="$re|Disabling lock debugging due to kernel taint"
# mixing mmap and direct I/O can generate a warning
re="$re|Page cache invalidation failure on direct I/O.*"
re="$re|File: /mnt/test.0/247 PID:*"
re="$re|dio_warn_stale_pagecache*"
egrep -v "($re)" | \
ignore_harmless_unwind_kasan_stack_oob | \
ignore_harmless_xfs_lockdep_warning