f2fs: recover wrong pino after checkpoint during fsync
authorJaegeuk Kim <jaegeuk.kim@samsung.com>
Thu, 13 Jun 2013 23:52:35 +0000 (08:52 +0900)
committerJaegeuk Kim <jaegeuk.kim@samsung.com>
Fri, 14 Jun 2013 00:04:45 +0000 (09:04 +0900)
commit354a3399dc6f7e556d04e1c731cd50e08eeb44bd
tree755e9c85c22dd0aa8dfdfc204e5697afd99b67af
parentb25958b6ecf1dce087e62b9aa27cf8f2fe9b5c86
f2fs: recover wrong pino after checkpoint during fsync

If a file is linked, f2fs loose its parent inode number so that fsync calls
for the linked file should do checkpoint all the time.
But, if we can recover its parent inode number after the checkpoint, we can
adjust roll-forward mechanism for the further fsync calls, which is able to
improve the fsync performance significatly.

Signed-off-by: Jaegeuk Kim <jaegeuk.kim@samsung.com>
fs/f2fs/dir.c
fs/f2fs/f2fs.h
fs/f2fs/file.c
fs/f2fs/namei.c
fs/f2fs/node.h
fs/f2fs/segment.c