| commit | 14ece1028b3ed53ffec1b1213ffc6acaf79ad77c | |
| author | Frank Mayhar <fmayhar@google.com> | |
| Mon, 17 May 2010 12:00:00 +0000 (17 08:00 -0400) | ||
| committer | Theodore Ts'o <tytso@mit.edu> | |
| Mon, 17 May 2010 12:00:00 +0000 (17 08:00 -0400) | ||
| tree | 8f5a13487139c68ef775c9d39b7be83386fdae06 | treesnapshot (tar.gz zip) |
| parent | 60e6679e28518ccd67169c4a539d8cc7490eb8a6 | commitdiff |
ext4: Make fsync sync new parent directories in no-journal mode
Add a new ext4 state to tell us when a file has been newly created; use
that state in ext4_sync_file in no-journal mode to tell us when we need
to sync the parent directory as well as the inode and data itself. This
fixes a problem in which a panic or power failure may lose the entire
file even when using fsync, since the parent directory entry is lost.
Addresses-Google-Bug: #2480057
Signed-off-by: Frank Mayhar <fmayhar@google.com>
Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
Add a new ext4 state to tell us when a file has been newly created; use
that state in ext4_sync_file in no-journal mode to tell us when we need
to sync the parent directory as well as the inode and data itself. This
fixes a problem in which a panic or power failure may lose the entire
file even when using fsync, since the parent directory entry is lost.
Addresses-Google-Bug: #2480057
Signed-off-by: Frank Mayhar <fmayhar@google.com>
Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
| fs/ext4/ext4.h | diffblobblamehistory | |
| fs/ext4/fsync.c | diffblobblamehistory | |
| fs/ext4/namei.c | diffblobblamehistory |