| commit | e03b07d9084d03e896b7f1a598a7f6aa18f6eeda | [log] [tgz] |
|---|---|---|
| author | Jaegeuk Kim <jaegeuk@kernel.org> | Wed Apr 01 19:38:20 2015 -0700 |
| committer | Jaegeuk Kim <jaegeuk@kernel.org> | Fri Apr 10 15:08:59 2015 -0700 |
| tree | 430a37a5bd068ca4ba05c4f7cd256b85edc74d91 | |
| parent | 418f6c277011d89c394309e72df9ad058e0a3f7d [diff] |
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>