LU-14769 e2fsck: init inode_badness proper for thread context

Some bad inode might be added before pass1, so global_ctx's
@inode_badness might be not NULL, we need init thread_ctx's
inode badness as NULL.

Change-Id: I31a526fd0cfc0c9f8c13598deba4ae882080412f
Signed-off-by: Wang Shilong <wshilong@ddn.com>
Reviewed-by: Andreas Dilger <adilger@whamcloud.com>
Reviewed-on: https://review.whamcloud.com/44012
Reviewed-by: Wang Shilong <wshilong@whamcloud.com>
Tested-by: Maloo <maloo@whamcloud.com>
Tested-by: jenkins <devops@whamcloud.com>

diff --git a/e2fsck/pass1.c b/e2fsck/pass1.c
index 93f8f23..5e97298 100644 (file)
--- a/e2fsck/pass1.c
+++ b/e2fsck/pass1.c
@@ -2990,6 +2990,7 @@ static errcode_t e2fsck_pass1_thread_prepare(e2fsck_t global_ctx, e2fsck_t *thre
        thread_context->block_dup_map = NULL;
        thread_context->casefolded_dirs = NULL;
        thread_context->expand_eisize_map = NULL;
+       thread_context->inode_badness = NULL;
 
        retval = e2fsck_allocate_block_bitmap(global_ctx->fs,
                                _("in-use block map"), EXT2FS_BMAP64_RBTREE,