summaryrefslogtreecommitdiffstats
path: root/fs/f2fs/recovery.c
diff options
context:
space:
mode:
authorJaegeuk Kim <jaegeuk@kernel.org>2015-04-01 19:38:20 -0700
committerJaegeuk Kim <jaegeuk@kernel.org>2015-04-10 15:08:59 -0700
commite03b07d9084d03e896b7f1a598a7f6aa18f6eeda (patch)
tree430a37a5bd068ca4ba05c4f7cd256b85edc74d91 /fs/f2fs/recovery.c
parent418f6c277011d89c394309e72df9ad058e0a3f7d (diff)
downloadlinux-e03b07d9084d03e896b7f1a598a7f6aa18f6eeda.tar.gz
linux-e03b07d9084d03e896b7f1a598a7f6aa18f6eeda.tar.bz2
linux-e03b07d9084d03e896b7f1a598a7f6aa18f6eeda.zip
f2fs: do not recover wrong data index
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 <jaegeuk@kernel.org>
Diffstat (limited to 'fs/f2fs/recovery.c')
-rw-r--r--fs/f2fs/recovery.c4
1 files changed, 3 insertions, 1 deletions
diff --git a/fs/f2fs/recovery.c b/fs/f2fs/recovery.c
index 63b720bd7e75..4b742c96c223 100644
--- a/fs/f2fs/recovery.c
+++ b/fs/f2fs/recovery.c
@@ -395,7 +395,9 @@ static int do_recover_data(struct f2fs_sb_info *sbi, struct inode *inode,
src = datablock_addr(dn.node_page, dn.ofs_in_node);
dest = datablock_addr(page, dn.ofs_in_node);
- if (src != dest && dest != NEW_ADDR && dest != NULL_ADDR) {
+ if (src != dest && dest != NEW_ADDR && dest != NULL_ADDR &&
+ dest >= MAIN_BLKADDR(sbi) && dest < MAX_BLKADDR(sbi)) {
+
if (src == NULL_ADDR) {
err = reserve_new_block(&dn);
/* We should not get -ENOSPC */