]> git.karo-electronics.de Git - karo-tx-linux.git/commit
ext4: Do not zero out uninitialized extents beyond i_size
authorDmitry Monakhov <dmonakhov@openvz.org>
Sun, 16 May 2010 10:00:00 +0000 (06:00 -0400)
committerPaul Gortmaker <paul.gortmaker@windriver.com>
Thu, 6 Jan 2011 23:07:35 +0000 (18:07 -0500)
commit36e647ecd1a71a982d9c8538e400e1a3bbf1b9cc
tree2385c9d0f93160e6154f2635068763b98d7f4e71
parentf33f28de02844deabcf785f3a0208b7c6058ff70
ext4: Do not zero out uninitialized extents beyond i_size

commit 21ca087a3891efab4d45488db8febee474d26c68 upstream.

The extents code will sometimes zero out blocks and mark them as
initialized instead of splitting an extent into several smaller ones.
This optimization however, causes problems if the extent is beyond
i_size because fsck will complain if there are uninitialized blocks
after i_size as this can not be distinguished from an inode that has
an incorrect i_size field.

https://bugzilla.kernel.org/show_bug.cgi?id=15742

Signed-off-by: Dmitry Monakhov <dmonakhov@openvz.org>
Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>
fs/ext4/extents.c