diff options
| author | Jaegeuk Kim <jaegeuk.kim@samsung.com> | 2013-03-21 15:21:57 +0900 |
|---|---|---|
| committer | Ziyan <jaraidaniel@gmail.com> | 2015-05-02 14:34:03 +0200 |
| commit | 90c09b9217fa429cd2c231f013374516b2d61bd4 (patch) | |
| tree | 5dee56f332ea9a2deaecdd88cd5a00f9a68d606a /fs/f2fs/f2fs.h | |
| parent | 63f440ed1302e9b5c26b2a0523096c63a9e7f73a (diff) | |
| download | kernel_samsung_tuna-90c09b9217fa429cd2c231f013374516b2d61bd4.zip kernel_samsung_tuna-90c09b9217fa429cd2c231f013374516b2d61bd4.tar.gz kernel_samsung_tuna-90c09b9217fa429cd2c231f013374516b2d61bd4.tar.bz2 | |
f2fs: fix to give correct parent inode number for roll forward
When we recover fsync'ed data after power-off-recovery, we should guarantee
that any parent inode number should be correct for each direct inode blocks.
So, let's make the following rules.
- The fsync should do checkpoint to all the inodes that were experienced hard
links.
- So, the only normal files can be recovered by roll-forward.
Signed-off-by: Jaegeuk Kim <jaegeuk.kim@samsung.com>
Conflicts:
fs/f2fs/file.c
Change-Id: I1c9798ad495bedbe7589d5146207dda2a51e812a
Diffstat (limited to 'fs/f2fs/f2fs.h')
| -rw-r--r-- | fs/f2fs/f2fs.h | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/fs/f2fs/f2fs.h b/fs/f2fs/f2fs.h index 7c76be2..f751e4f 100644 --- a/fs/f2fs/f2fs.h +++ b/fs/f2fs/f2fs.h @@ -148,6 +148,7 @@ struct extent_info { * i_advise uses FADVISE_XXX_BIT. We can add additional hints later. */ #define FADVISE_COLD_BIT 0x01 +#define FADVISE_CP_BIT 0x02 struct f2fs_inode_info { struct inode vfs_inode; /* serve a vfs inode */ @@ -825,7 +826,6 @@ static inline int f2fs_clear_bit(unsigned int nr, char *addr) /* used for f2fs_inode_info->flags */ enum { FI_NEW_INODE, /* indicate newly allocated inode */ - FI_NEED_CP, /* need to do checkpoint during fsync */ FI_INC_LINK, /* need to increment i_nlink */ FI_ACL_MODE, /* indicate acl mode */ FI_NO_ALLOC, /* should not allocate any blocks */ |