lkml.org 
[lkml]   [2019]   [Aug]   [5]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
Patch in this message
/
From
Subject[f2fs-dev] [PATCH] fsck.f2fs: fix the bug in reserve_new_block
Date
if we new node block in fsck flow, we need to update
the valid_node_cnt at the same time.

Signed-off-by: Lihong Kou <koulihong@huawei.com>
---
fsck/segment.c | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/fsck/segment.c b/fsck/segment.c
index 98c836e..c16fb3a 100644
--- a/fsck/segment.c
+++ b/fsck/segment.c
@@ -51,8 +51,11 @@ void reserve_new_block(struct f2fs_sb_info *sbi, block_t *to,

if (old_blkaddr == NULL_ADDR) {
sbi->total_valid_block_count++;
- if (c.func == FSCK)
+ if (c.func == FSCK) {
fsck->chk.valid_blk_cnt++;
+ if (IS_NODESEG(type))
+ fsck->chk.valid_node_cnt++;
+ }
}
se->dirty = 1;

--
2.7.4
\
 
 \ /
  Last update: 2019-08-05 09:20    [W:0.040 / U:1.200 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site