Revert "f2fs: do not recover from previous remained wrong dnodes"
authorChao Yu <yuchao0@huawei.com>
Sat, 5 Nov 2016 03:12:40 +0000 (11:12 +0800)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Wed, 23 Jan 2019 07:10:53 +0000 (08:10 +0100)
commitfe6b4e4083b24dc8a98a3493068a5fb3cde6a865
tree199269e42cc35e4957de3eacb27e934fc669fbc4
parentd379b338387e3d5a9b5ebe5ab16656a9c65c988d
Revert "f2fs: do not recover from previous remained wrong dnodes"

commit d47b8715953ad0cf82bb0a9d30d7b11d83bc9c11 upstream.

i_times of inode will be set with current system time which can be
configured through 'date', so it's not safe to judge dnode block as
garbage data or unchanged inode depend on i_times.

Now, we have used enhanced 'cp_ver + cp' crc method to verify valid
dnode block, so I expect recoverying invalid dnode is almost not
possible.

This reverts commit 807b1e1c8e08452948495b1a9985ab46d329e5c2.

Signed-off-by: Chao Yu <yuchao0@huawei.com>
Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
Cc: Ben Hutchings <ben.hutchings@codethink.co.uk>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
fs/f2fs/recovery.c