Benjamin LaHaise <bcrl@xxxxxxxxx> writes: > Does someone already have a simple test case we can add to the libaio test > suite to verify this behaviour? I can't reproduce this problem using a loop device, which is what the libaio test suite uses. Even when using real hardware, you have to have disks that are slow enough in order for this to trigger reliably (or at all). Given those two points, I think it might make sense to continue to use xfstests to find this problem for us, since it already has the infrastructure in place to test real devices and since it already triggers the problem. I could write a more targeted test within xfstests, but I don't think that's strictly necessary (it would just make it more clear what the expectations are, and maybe bump the hit rate percentage up). Cheers, Jeff -- To unsubscribe from this list: send the line "unsubscribe fstests" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
