Re: [PATCH] f2fs: fix to determine start_cp_addr by sbi->cur_cp_pack

On 12/10, Chao Yu wrote: > Hi Jaegeuk, > > Let me try to understand this, in some cases, we can write a checkpoint pack > which has wrong cp_ver, like in 1st cp pack which has even version number or > 2nd > cp pack which has odd version number, so if we load that kind of cp pack > during > fill_

Re: [PATCH] f2fs: fix to determine start_cp_addr by sbi->cur_cp_pack

Hi Jaegeuk, Let me try to understand this, in some cases, we can write a checkpoint pack which has wrong cp_ver, like in 1st cp pack which has even version number or 2nd cp pack which has odd version number, so if we load that kind of cp pack during fill_super, we may load wrong summary data from

[PATCH] f2fs: fix to determine start_cp_addr by sbi->cur_cp_pack

We don't guarantee cp_addr is fixed by cp_version. This is to sync with f2fs-tools. Cc: sta...@vger.kernel.org Signed-off-by: Jaegeuk Kim --- fs/f2fs/checkpoint.c | 5 + fs/f2fs/f2fs.h | 14 +++--- 2 files changed, 8 insertions(+), 11 deletions(-) diff --git a/fs/f2fs/checkpo