f2fs: do not set LOST_PINO for newly created dir

Since directories will be written back with checkpoint and fsync a
directory will always write CP, there is no need to set LOST_PINO
after creating a directory.

Signed-off-by: Sheng Yong <shengyong1@huawei.com>
Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>

diff --git a/fs/f2fs/dir.c b/fs/f2fs/dir.c
index 94756f55a97e7d86052cdb49ce79fcc131738cfd..37f9c7f556058fcda91b15b411acfeebdf48824d 100644 (file)
--- a/fs/f2fs/dir.c
+++ b/fs/f2fs/dir.c
@@ -415,7 +415,8 @@ struct page *init_inode_metadata(struct inode *inode, struct inode *dir,
         * We lost i_pino from now on.
         */
        if (is_inode_flag_set(inode, FI_INC_LINK)) {
-               file_lost_pino(inode);
+               if (!S_ISDIR(inode->i_mode))
+                       file_lost_pino(inode);
                /*
                 * If link the tmpfile to alias through linkat path,
                 * we should remove this inode from orphan list.