| commit | 56fcad29d4b3cbcbb2ed47a9d3ceca3f57175417 | |
| author | Jan Kara <jack@suse.cz> | |
| Tue, 8 Sep 2009 12:59:42 +0000 (8 14:59 +0200) | ||
| committer | Jan Kara <jack@suse.cz> | |
| Wed, 16 Sep 2009 15:44:11 +0000 (16 17:44 +0200) | ||
| tree | 4ad4816b11706e350760a3e206126105a7bf9a5c | treesnapshot (tar.gz zip) |
| parent | 4f003fd32bc54ec438b8691795279844df27ce38 | commitdiff |
ext3: Flush disk caches on fsync when needed
In case we fsync() a file and inode is not dirty, we don't force a transaction
to disk and hence don't flush disk caches. Thus file data could be just in disk
caches and not on persistent storage. Fix the problem by flushing disk caches
if we didn't force a transaction commit.
Signed-off-by: Jan Kara <jack@suse.cz>
In case we fsync() a file and inode is not dirty, we don't force a transaction
to disk and hence don't flush disk caches. Thus file data could be just in disk
caches and not on persistent storage. Fix the problem by flushing disk caches
if we didn't force a transaction commit.
Signed-off-by: Jan Kara <jack@suse.cz>
| fs/ext3/fsync.c | diffblobblamehistory |