On Mon, Sep 23, 2013 at 10:35:18AM -0400, Eric Whitney wrote: > Commit d3f32c2db8 was intended to detect extents found outside their > proper location in the extent tree, including invalid extents at the > end of an extent block. However, it incorrectly reported legal > uninitialized extents created by fallocate() at the end of file with > the FALLOC_FL_KEEP_SIZE flag as false positives. xfstests > generic/263 (among others) caught this problem, while the e2fsprogs > test f_uninit_ext_past_eof did not. The latter test failed to > detect the problem in part because it uses a test file whose i_size > is 0. > > Add a test derived from the fsx-based test case in xfstests > generic/263 consisting of a file with non-zero length, more than > four extents total, and two uninitialized extents past EOF to > reliably reproduce commit d3f32c2db8's false positive behavior. > > Signed-off-by: Eric Whitney <enwlinux@xxxxxxxxx> Applied, thanks. - Ted -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
