BMC/Intel-BMC/linux.git/fs/f2fs/recovery.c, branch dev

f2fs: hide common code in f2fs_replace_block

2015-06-02T16:52:07+00:00

This patch clean up codes through: 1.rename f2fs_replace_block to __f2fs_replace_block(). 2.introduce new f2fs_replace_block() to include __f2fs_replace_block() and some common related codes around __f2fs_replace_block(). Then, newly introduced function f2fs_replace_block can be used by following patch. Signed-off-by: Chao Yu Signed-off-by: Jaegeuk Kim

f2fs crypto: add filename encryption for roll-forward recovery

2015-05-28T22:41:55+00:00

This patch adds a bit flag to indicate whether or not i_name in the inode is encrypted. If this name is encrypted, we can't do recover_dentry during roll-forward. So, f2fs_sync_file() needs to do checkpoint, if this will be needed in future. Signed-off-by: Jaegeuk Kim

f2fs: introduce f2fs_replace_block() for reuse

2015-05-28T22:41:42+00:00

Introduce a generic function replace_block base on recover_data_page, and export it. So with it we can operate file's meta data which is in CP/SSA area when we invoke fallocate with FALLOC_FL_COLLAPSE_RANGE flag. Signed-off-by: Chao Yu Signed-off-by: Jaegeuk Kim

f2fs: use is_valid_blkaddr to verify blkaddr for readability

2015-05-07T18:38:32+00:00

Export is_valid_blkaddr() and use it to replace some codes for readability. Signed-off-by: Chao Yu Signed-off-by: Jaegeuk Kim

f2fs: pass checkpoint reason on roll-forward recovery

2015-04-16T16:45:40+00:00

This patch adds CP_RECOVERY to remain recovery information for checkpoint. And, it makes sure writing checkpoint in this case. Signed-off-by: Jaegeuk Kim

f2fs: do not recover wrong data index

2015-04-10T22:08:59+00:00

During the roll-forward recovery, if we found a new data index written fsync lastly, we need to recover new block address. But, if that address was corrupted, we should not recover that. Otherwise, f2fs gets kernel panic from: In check_index_in_prev_nodes(), sentry = get_seg_entry(sbi, segno); --------------------------> out-of-range segno. Signed-off-by: Jaegeuk Kim

f2fs: do not increase link count during recovery

2015-04-10T22:08:58+00:00

If there are multiple fsynced dnodes having a dent flag, roll-forward routine sets FI_INC_LINK for their inode, and recovery_dentry increases its link count accordingly. That results in normal file having a link count as 2, so we can't unlink those files. This was added to handle several inode blocks having same inode number with different directory paths. But, current f2fs doesn't replay all of path changes and only recover its dentry for the last fsynced inode block. So, there is no reason to do this. Signed-off-by: Jaegeuk Kim

f2fs: add F2FS_INLINE_DOTS to recover missing dot dentries

2015-04-10T22:08:57+00:00

If f2fs was corrupted with missing dot dentries, it needs to recover them after fsck.f2fs detection. The underlying precedure is: 1. The fsck.f2fs remains F2FS_INLINE_DOTS flag in directory inode, if it detects missing dot dentries. 2. When f2fs looks up the corrupted directory, it triggers f2fs_add_link with proper inode numbers and their dot and dotdot names. 3. Once f2fs recovers the directory without errors, it removes F2FS_INLINE_DOTS finally. Signed-off-by: Jaegeuk Kim

f2fs: fix mismatching lock and unlock pages for roll-forward recovery

2015-04-10T22:08:56+00:00

Previously, inode page is not correctly locked and unlocked in pair during the roll-forward recovery. Signed-off-by: Jaegeuk Kim

f2fs: split set_data_blkaddr from f2fs_update_extent_cache

2015-04-10T22:08:49+00:00

Split __set_data_blkaddr from f2fs_update_extent_cache for readability. Additionally rename __set_data_blkaddr to set_data_blkaddr for exporting. Signed-off-by: Chao Yu Signed-off-by: Jaegeuk Kim