@@ -127,9 +127,11 @@ filter_xfs_dmesg()
local warn1="WARNING:.*fs/xfs/xfs_file\.c:.*xfs_file_dio_aio_write.*"
local warn2="WARNING:.*fs/xfs/xfs_file\.c:.*xfs_file_dio_aio_read.*"
local warn3="WARNING:.*fs/xfs/xfs_file\.c:.*xfs_file_read_iter.*"
+ local warn4="WARNING:.*fs/xfs/xfs_file\.c:.*xfs_file_aio_read.*"
sed -e "s#$warn1#Intentional warnings in xfs_file_dio_aio_write#" \
-e "s#$warn2#Intentional warnings in xfs_file_dio_aio_read#" \
- -e "s#$warn3#Intentional warnings in xfs_file_read_iter#"
+ -e "s#$warn3#Intentional warnings in xfs_file_read_iter#" \
+ -e "s#$warn4#Intentional warnings in xfs_file_aio_read#"
}
# umount before checking dmesg in case umount triggers any WARNING or Oops
Current generic/095 warning whitelist include: "xfs_file_dio_aio_read" and "xfs_file_read_iter" But from the history we can see: 1) xfs_file_dio_aio_read() was splited from xfs_file_read_iter() by below commit: bbc5a74 xfs: split xfs_file_read_iter into buffered and direct I/O helpers 2) xfs_file_read_iter() came from xfs_file_aio_read() as below commit: b4f5d2c xfs: switch to ->read_iter() Some Linux distro (e.g: RHEL-7) still use the old kernel with old function xfs_file_aio_read(). Signed-off-by: Zorro Lang <zlang@redhat.com> --- tests/generic/095 | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-)