Eric Sandeen wrote:
We saw problems w/ xfs doing AIO+DIO into a sparse file. https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=217098 It seemed that xfs was doing "extent conversion" at the wrong offsets, so written regions came up as unwritten (zeros) and stale data was exposed in the region after the write. Thanks to Peter Backes for the very nice testcase. This also broke xen with blktap over xfs.
Hrmph. Zach's changes in -mm magically made this go away... I was about to submit a proper patch against -mm but it seem to be not needed.
So, now digging around to see why that is, and what exactly "fixed" things. -Eric - To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html