The first three patches make fsx use fallocate/fpunch correctly. Hole punching is not detected correctly, falloc/fpunch operations can't actually be executed properly, and the logdump code will segv on the first falloc operation it finds in the log. The last patch widens the fsx coverage to mix direct IO reads/writes with mmapped reads/writes as that was the test case that it was executing (instead of using falloc/fpunch!) when it triggered the error (a real bug) that lead to me finding this mess.... _______________________________________________ xfs mailing list xfs@xxxxxxxxxxx http://oss.sgi.com/mailman/listinfo/xfs
