f2fs: fix wrong written_valid_blocks counting
authorJaegeuk Kim <jaegeuk@kernel.org>
Tue, 15 Nov 2016 02:20:10 +0000 (18:20 -0800)
committerJaegeuk Kim <jaegeuk@google.com>
Mon, 25 Sep 2017 22:13:34 +0000 (15:13 -0700)
commitdf3f20f12b9fcf4c93706ac24edcb6a3ff9f58a5
treeb18fbfba86aaec4b0ef327d19aa5079469f5cf21
parent79ba046b115eaa4c0f30104bccb6f41ae710e952
f2fs: fix wrong written_valid_blocks counting

commit c79b7ff1d3c7710c23d8828a69d8cbc5597ad19f upstream.

Previously, written_valid_blocks was got by ckpt->valid_block_count. But if
the last checkpoint has some NEW_ADDR due to power-cut, we can get wrong value.
Fix it to get the number from actual written block count from sit entries.

Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
fs/f2fs/segment.c