diff options
| author |   Dmitry Monakhov <dmonakhov@openvz.org> | 2014-08-27 18:40:00 -0400 |
|---|---|---|
| committer |   Theodore Ts'o <tytso@mit.edu> | 2014-08-27 18:40:00 -0400 |
| commit | c174e6d6979a04b7b77b93f244396be4b81f8bfb (patch) | |
| tree | 2a4b4b6e339268948f04f0940f17a33e3bb72d88 /tools/perf/scripts/python/export-to-postgresql.py | |
| parent | ext4: fix incorect journal credits reservation in ext4_zero_range (diff) | |
| download | wireguard-linux-c174e6d6979a04b7b77b93f244396be4b81f8bfb.tar.xz wireguard-linux-c174e6d6979a04b7b77b93f244396be4b81f8bfb.zip | |
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
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions