ext4: fix transaction issues for ext4_fallocate and ext_zero_range
authorDmitry Monakhov <dmonakhov@openvz.org>
Wed, 27 Aug 2014 22:40:00 +0000 (18:40 -0400)
committerTheodore Ts'o <tytso@mit.edu>
Wed, 27 Aug 2014 22:40:00 +0000 (18:40 -0400)
commitc174e6d6979a04b7b77b93f244396be4b81f8bfb
tree2a4b4b6e339268948f04f0940f17a33e3bb72d88
parent69dc9536405213c1d545fcace1fc15c481d00aae
ext4: fix transaction issues for ext4_fallocate and ext_zero_range

After commit f282ac19d86f we use different transactions for
preallocation and i_disksize update which result in complain from fsck
after power-failure.  spotted by generic/019. IMHO this is regression
because fs becomes inconsistent, even more 'e2fsck -p' will no longer
works (which drives admins go crazy) Same transaction requirement
applies ctime,mtime updates

testcase: xfstest generic/019

Signed-off-by: Dmitry Monakhov <dmonakhov@openvz.org>
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
Cc: stable@vger.kernel.org
fs/ext4/extents.c