summaryrefslogtreecommitdiffstats
path: root/fs/f2fs/recovery.c
diff options
context:
space:
mode:
authorJaegeuk Kim <jaegeuk@kernel.org>2014-08-15 18:56:46 +0200
committerJaegeuk Kim <jaegeuk@kernel.org>2014-08-21 22:57:02 +0200
commit202095a7a0ec075b924cb15dde330bf76e485f61 (patch)
treeb449ff58a4ba996bb6c3505c3fb5cbbe6ddea847 /fs/f2fs/recovery.c
parentf2fs: avoid double lock in truncate_blocks (diff)
downloadlinux-202095a7a0ec075b924cb15dde330bf76e485f61.tar.xz
linux-202095a7a0ec075b924cb15dde330bf76e485f61.zip
f2fs: remove rewrite_node_page
I think we need to let the dirty node pages remain in the page cache instead of rewriting them in their places. So, after done with successful recovery, write_checkpoint will flush all of them through the normal write path. Through this, we can avoid potential error cases in terms of block allocation. Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
Diffstat (limited to 'fs/f2fs/recovery.c')
-rw-r--r--fs/f2fs/recovery.c2
1 files changed, 0 insertions, 2 deletions
diff --git a/fs/f2fs/recovery.c b/fs/f2fs/recovery.c
index d36ef35353b2..756c41cd2582 100644
--- a/fs/f2fs/recovery.c
+++ b/fs/f2fs/recovery.c
@@ -371,8 +371,6 @@ static int do_recover_data(struct f2fs_sb_info *sbi, struct inode *inode,
fill_node_footer(dn.node_page, dn.nid, ni.ino,
ofs_of_node(page), false);
set_page_dirty(dn.node_page);
-
- recover_node_page(sbi, dn.node_page, &sum, &ni, blkaddr);
err:
f2fs_put_dnode(&dn);
f2fs_unlock_op(sbi);