From: Jaegeuk Kim <jaegeuk.kim@samsung.com>
Date: Thu, 21 Mar 2013 06:21:57 +0000 (+0900)
Subject: f2fs: fix to give correct parent inode number for roll forward
X-Git-Tag: v3.10-rc1~45^2~44
X-Git-Url: http://git.openpandora.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=953a3e27e10fc6acb480801ea47197d0270d735e;p=pandora-kernel.git

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>
---

Reading git-diff-tree failed