diff options
| author | Jan Kara <jack@suse.cz> | 2012-09-26 21:52:20 -0400 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2012-10-13 05:28:10 +0900 |
| commit | a6c0070c1f5a6c7b0bba5bb5be44b1dabe88af56 (patch) | |
| tree | dcba98390e77e1f4a75e9aaafab668f72e17ebeb /MAINTAINERS | |
| parent | 985f704d74944dc66b5185aa9ccebcb936f2b8e0 (diff) | |
| download | kernel_samsung_smdk4412-a6c0070c1f5a6c7b0bba5bb5be44b1dabe88af56.zip kernel_samsung_smdk4412-a6c0070c1f5a6c7b0bba5bb5be44b1dabe88af56.tar.gz kernel_samsung_smdk4412-a6c0070c1f5a6c7b0bba5bb5be44b1dabe88af56.tar.bz2 | |
ext4: fix fdatasync() for files with only i_size changes
commit b71fc079b5d8f42b2a52743c8d2f1d35d655b1c5 upstream.
Code tracking when transaction needs to be committed on fdatasync(2) forgets
to handle a situation when only inode's i_size is changed. Thus in such
situations fdatasync(2) doesn't force transaction with new i_size to disk
and that can result in wrong i_size after a crash.
Fix the issue by updating inode's i_datasync_tid whenever its size is
updated.
Reported-by: Kristian Nielsen <knielsen@knielsen-hq.org>
Signed-off-by: Jan Kara <jack@suse.cz>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'MAINTAINERS')
0 files changed, 0 insertions, 0 deletions