tree 8b7c8b192d237ee774c0f1ab59f3a0007e463655
parent 64aa7ed98db489d1c41ef140876ada38498678ab
author Jaegeuk Kim <jaegeuk.kim@samsung.com> 1369012229 +0900
committer Jaegeuk Kim <jaegeuk.kim@samsung.com> 1369720982 +0900

f2fs: update inode page after creation

I found a bug when testing power-off-recovery as follows.

[Bug Scenario]
1. create a file
2. fsync the file
3. reboot w/o any sync
4. try to recover the file
 - found its fsync mark
 - found its dentry mark
   : try to recover its dentry
    - get its file name
    - get its parent inode number
     : here we got zero value

The reason why we get the wrong parent inode number is that we didn't
synchronize the inode page with its newly created inode information perfectly.

Especially, previous f2fs stores fi->i_pino and writes it to the cached
node page in a wrong order, which incurs the zero-valued i_pino during the
recovery.

So, this patch modifies the creation flow to fix the synchronization order of
inode page with its inode.

Signed-off-by: Jaegeuk Kim <jaegeuk.kim@samsung.com>