Reference in a new issue

Blame

Copy permalink

Reference in a new issue

Copy permalink

Jan Kara c404f0dee7 ext4: fix fdatasync(2) after extent manipulation operations ...

commit 67a7d5f561 upstream.

Currently, extent manipulation operations such as hole punch, range
zeroing, or extent shifting do not record the fact that file data has
changed and thus fdatasync(2) has a work to do. As a result if we crash
e.g. after a punch hole and fdatasync, user can still possibly see the
punched out data after journal replay. Test generic/392 fails due to
these problems.

Fix the problem by properly marking that file data has changed in these
operations.

Fixes: a4bb6b64e3
Signed-off-by: Jan Kara <jack@suse.cz>
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

2017-06-14 15:05:58 +02:00

5959 lines

163 KiB

Raw Permalink Blame History