[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1586342714-12536-45-git-send-email-wangshilong1991@gmail.com>
Date: Wed, 8 Apr 2020 19:45:12 +0900
From: Wang Shilong <wangshilong1991@...il.com>
To: linux-ext4@...r.kernel.org
Cc: lixi@....com, adilger@...ger.ca, sihara@....com,
Wang Shilong <wshilong@....com>
Subject: [RFC PATCH 44/46] e2fsck: reset lost_and_found after threads finish
From: Wang Shilong <wshilong@....com>
This should not be kept, the reaons is similar to what
e2fsck_pass1 has done before.
Signed-off-by: Wang Shilong <wshilong@....com>
---
e2fsck/pass1.c | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/e2fsck/pass1.c b/e2fsck/pass1.c
index 19475815..61b667e0 100644
--- a/e2fsck/pass1.c
+++ b/e2fsck/pass1.c
@@ -3007,6 +3007,11 @@ static errcode_t e2fsck_pass1_merge_context(e2fsck_t global_ctx,
global_ctx->flags |= thread_ctx->flags;
/* threads might enable E2F_OPT_YES */
global_ctx->options |= thread_ctx->options;
+ /*
+ * The l+f inode may have been cleared, so zap it now and
+ * later passes will recalculate it if necessary
+ */
+ global_ctx->lost_and_found = 0;
e2fsck_pass1_merge_dir_info(global_ctx, thread_ctx);
e2fsck_pass1_merge_dx_dir(global_ctx, thread_ctx);
--
2.25.2
Powered by blists - more mailing lists