Commit d58dfb75 authored by Sheng Yong's avatar Sheng Yong Committed by Jaegeuk Kim

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: default avatarSheng Yong <shengyong1@huawei.com>
Signed-off-by: default avatarJaegeuk Kim <jaegeuk@kernel.org>
parent 0771fcc7
...@@ -415,7 +415,8 @@ struct page *init_inode_metadata(struct inode *inode, struct inode *dir, ...@@ -415,7 +415,8 @@ struct page *init_inode_metadata(struct inode *inode, struct inode *dir,
* We lost i_pino from now on. * We lost i_pino from now on.
*/ */
if (is_inode_flag_set(inode, FI_INC_LINK)) { 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, * If link the tmpfile to alias through linkat path,
* we should remove this inode from orphan list. * we should remove this inode from orphan list.
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment