diff options
| author | Sheng Yong <shengyong1@huawei.com> | 2017-06-26 10:41:36 +0800 |
|---|---|---|
| committer | Moyster <oysterized@gmail.com> | 2017-07-21 12:38:12 +0200 |
| commit | 2f26d368a291d25733151f70d9cc46f2b085acf9 (patch) | |
| tree | 40d2c12cb582abe8a7a1f4d10a7c259ce4629da6 /kernel | |
| parent | d2c2bd2d940373e5ef81a1c0588323d779cfe0ef (diff) | |
f2fs: do not set LOST_PINO for renamed dir
After renaming a directory, fsck could detect unmatched pino. The scenario
can be reproduced as the following:
$ mkdir /bar/subbar /foo
$ rename /bar/subbar /foo
Then fsck will report:
[ASSERT] (__chk_dots_dentries:1182) --> Bad inode number[0x3] for '..', parent parent ino is [0x4]
Rename sets LOST_PINO for old_inode. However, the flag cannot be cleared,
since dir is written back with CP. So, let's get rid of LOST_PINO for a
renamed dir and fix the pino directly at the end of rename.
Signed-off-by: Sheng Yong <shengyong1@huawei.com>
Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
Diffstat (limited to 'kernel')
0 files changed, 0 insertions, 0 deletions