diff options
| author | Chao Yu <yuchao0@huawei.com> | 2018-02-03 17:44:39 +0800 |
|---|---|---|
| committer | Jaegeuk Kim <jaegeuk@kernel.org> | 2018-03-13 08:05:40 +0900 |
| commit | fb0e72c8b94903be3a7e742ab0a4b53b89e7ee35 (patch) | |
| tree | fdbc7f7837aeec1a0f453a17b2640cb41249bc4b /fs/f2fs/data.c | |
| parent | 0f9ec2a8f65d72a454e99fb4f7351d7e01070385 (diff) | |
f2fs: fix to handle looped node chain during recovery
There is no checksum in node block now, so bit-transition from hardware
can make node_footer.next_blkaddr being corrupted w/o any detection,
result in node chain becoming looped one.
For this condition, during recovery, in order to avoid running into dead
loop, let's detect it and just skip out.
Signed-off-by: Yunlei He <heyunlei@huawei.com>
Signed-off-by: Chao Yu <yuchao0@huawei.com>
Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
Diffstat (limited to 'fs/f2fs/data.c')
0 files changed, 0 insertions, 0 deletions