summaryrefslogtreecommitdiffstats
path: root/include/soc
diff options
context:
space:
mode:
authorJaegeuk Kim <jaegeuk@kernel.org>2015-04-01 19:38:20 -0700
committerJaegeuk Kim <jaegeuk@kernel.org>2015-04-10 15:08:59 -0700
commite03b07d9084d03e896b7f1a598a7f6aa18f6eeda (patch)
tree430a37a5bd068ca4ba05c4f7cd256b85edc74d91 /include/soc
parent418f6c277011d89c394309e72df9ad058e0a3f7d (diff)
downloadlinux-e03b07d9084d03e896b7f1a598a7f6aa18f6eeda.tar.bz2
f2fs: do not recover wrong data index
During the roll-forward recovery, if we found a new data index written fsync lastly, we need to recover new block address. But, if that address was corrupted, we should not recover that. Otherwise, f2fs gets kernel panic from: In check_index_in_prev_nodes(), sentry = get_seg_entry(sbi, segno); --------------------------> out-of-range segno. Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
Diffstat (limited to 'include/soc')
0 files changed, 0 insertions, 0 deletions