Hi Amir, We reported these bugs separately on the two mailing lists because, though the workload was the same, the behavior/bug was different on the two filesystems. On ext4 there was data loss, while on xfs the fzero operation was not persisted even after a fsync. On Tue, Mar 13, 2018 at 1:36 AM, Amir Goldstein <amir73il@xxxxxxxxx> wrote: > Since the exact same report was sent to the ext4 list, CC'ing Dave's response to > Ted and fstests, which seems an appropriate crowd for this discussion. > I think that future CrashMonkey findings should be CC'ed to either fsdevel > or fstests, especially if more than one filesystem is affected. Thanks for the suggestion. We will CC our future reports to these lists. Thanks, Jayashree -- 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
