f2fs: move sanity checking of cp into get_valid_checkpoint
authorShawn Lin <shawn.lin@rock-chips.com>
Wed, 17 Feb 2016 03:26:32 +0000 (11:26 +0800)
committerJaegeuk Kim <jaegeuk@kernel.org>
Tue, 23 Feb 2016 05:39:56 +0000 (21:39 -0800)
commit984ec63c5a82a07ad4490ecc69bebacd23f6fa64
treec82497b491d16a1b48d812319fbba0e04e755b19
parent2b39e9072d79ab2525100413f3f7a0b8a3e15873
f2fs: move sanity checking of cp into get_valid_checkpoint

>From the function name of get_valid_checkpoint, it seems to return
the valid cp or NULL for caller to check. If no valid one is found,
f2fs_fill_super will print the err log. But if get_valid_checkpoint
get one valid(the return value indicate that it's valid, however actually
it is invalid after sanity checking), then print another similar err
log. That seems strange. Let's keep sanity checking inside the procedure
of geting valid cp. Another improvement we gained from this move is
that even the large volume is supported, we check the cp in advanced
to skip the following procedure if failing the sanity checking.

Signed-off-by: Shawn Lin <shawn.lin@rock-chips.com>
Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
fs/f2fs/checkpoint.c
fs/f2fs/f2fs.h
fs/f2fs/super.c