Darrick,
I may have hit an xfs regression that shows up in 4.16 that fails
xfstest xfs/348. I have bisected it to this commit:
9cfb9b47479e237d217dbcfafe034cbf98f45909 ("xfs: provide a centralized
method for verifying inline fork data")
# ./check xfs/348
FSTYP -- xfs (non-debug)
PLATFORM -- Linux/x86_64 skx-ntbusd 4.15.0-rc7+
MKFS_OPTIONS -- -f -bsize=4096 /dev/pmem0p2
MOUNT_OPTIONS -- -o context=system_u:object_r:root_t:s0 /dev/pmem0p2
/mnt/xfstests_scratch
xfs/348 29s ... - output mismatch (see
/root/xfstests/xfstests-dev/results//xfs/348.out.bad)
--- tests/xfs/348.out 2017-10-19 10:57:22.561819578 -0700
+++ /root/xfstests/xfstests-dev/results//xfs/348.out.bad
2018-05-21 17:13:39.171256163 -0700
@@ -239,7 +239,7 @@
would have junked entry "DIR" in directory PARENT_INO
would have junked entry "EMPTY" in directory PARENT_INO
would have junked entry "FIFO" in directory PARENT_INO
-stat: 'SCRATCH_MNT/test/DIR' is a symbolic link
+stat: cannot stat 'SCRATCH_MNT/test/DIR': Structure needs cleaning
stat: 'SCRATCH_MNT/test/DATA' is a symbolic link
stat: cannot stat 'SCRATCH_MNT/test/EMPTY': Structure needs cleaning
...
(Run 'diff -u tests/xfs/348.out
/root/xfstests/xfstests-dev/results//xfs/348.out.bad' to see the entire
diff)
Ran: xfs/348
Failures: xfs/348
Failed 1 of 1 tests
--
Dave Jiang
Software Engineer, SSG/OTC
Intel Corp.
dave.jiang@xxxxxxxxx
--
To unsubscribe from this list: send the line "unsubscribe linux-xfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
