aboutsummaryrefslogtreecommitdiffstats
path: root/fs/nfs/write.c
diff options
context:
space:
mode:
authorTheodore Ts'o <tytso@mit.edu>2010-05-17 00:00:00 -0400
committerTheodore Ts'o <tytso@mit.edu>2010-05-17 00:00:00 -0400
commit786ec7915e530936b9eb2e3d12274145cab7aa7d (patch)
treebbdfd4189ef769196808698e68862d4a192595e6 /fs/nfs/write.c
parentf70f362b4a6fe47c239dbfb3efc0cc2c10e4f09c (diff)
ext4: Clear the EXT4_EOFBLOCKS_FL flag only when warranted
Dimitry Monakhov discovered an edge case where it was possible for the EXT4_EOFBLOCKS_FL flag could get cleared unnecessarily. This is true; I have a test case that can be exercised via downloading and decompressing the file: wget ftp://ftp.kernel.org/pub/linux/kernel/people/tytso/ext4-testcases/eofblocks-fl-test-case.img.bz2 bunzip2 eofblocks-fl-test-case.img dd if=/dev/zero of=eofblocks-fl-test-case.img bs=1k seek=17925 bs=1k count=1 conv=notrunc However, triggering it in real life is highly unlikely since it requires an extremely fragmented sparse file with a hole in exactly the right place in the extent tree. (It actually took quite a bit of work to generate this test case.) Still, it's nice to get even extreme corner cases to be correct, so this patch makes sure that we don't clear the EXT4_EOFBLOCKS_FL incorrectly even in this corner case. Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
Diffstat (limited to 'fs/nfs/write.c')
0 files changed, 0 insertions, 0 deletions