From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-9.6 required=3.0 tests=DKIM_INVALID,DKIM_SIGNED, HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_PATCH,MAILING_LIST_MULTI,SIGNED_OFF_BY, SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED,USER_AGENT_GIT autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 2735FC0650F for ; Mon, 5 Aug 2019 07:20:45 +0000 (UTC) Received: from lists.sourceforge.net (lists.sourceforge.net [216.105.38.7]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id EA311205F4; Mon, 5 Aug 2019 07:20:44 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=fail reason="signature verification failed" (1024-bit key) header.d=sourceforge.net header.i=@sourceforge.net header.b="Vl35lOIT"; dkim=fail reason="signature verification failed" (1024-bit key) header.d=sf.net header.i=@sf.net header.b="OS6Uu5a8" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org EA311205F4 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=huawei.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=linux-f2fs-devel-bounces@lists.sourceforge.net Received: from [127.0.0.1] (helo=sfs-ml-1.v29.lw.sourceforge.com) by sfs-ml-1.v29.lw.sourceforge.com with esmtp (Exim 4.90_1) (envelope-from ) id 1huXIS-00088i-1O; Mon, 05 Aug 2019 07:20:44 +0000 Received: from [172.30.20.202] (helo=mx.sourceforge.net) by sfs-ml-1.v29.lw.sourceforge.com with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.90_1) (envelope-from ) id 1huXIO-00087v-Ns for linux-f2fs-devel@lists.sourceforge.net; Mon, 05 Aug 2019 07:20:40 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=sourceforge.net; s=x; h=Content-Type:MIME-Version:Message-ID:Date:Subject: CC:To:From:Sender:Reply-To:Content-Transfer-Encoding:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:In-Reply-To:References:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=/G4mlcdCjEDcCfoCDyvwYk54S0cPAHtPygbPefU/jAg=; b=Vl35lOITQu58EFgOcPJMQEo47y 0B5OgJmcjrnR4ZX2d5UgPB/Qpv7IOwtoGVNwLPU+M84j8JORVVZDJL0llJhOJ+Cp+S+0wtjIQThPq s9aJ2qLfR84k7jGZm0OEBAdjsytVBgsW64KEZCCnBEvrCv/w6JjnLTPgPvs30xQ/98c8=; DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=sf.net; s=x ; h=Content-Type:MIME-Version:Message-ID:Date:Subject:CC:To:From:Sender: Reply-To:Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date :Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To: References:List-Id:List-Help:List-Unsubscribe:List-Subscribe:List-Post: List-Owner:List-Archive; bh=/G4mlcdCjEDcCfoCDyvwYk54S0cPAHtPygbPefU/jAg=; b=O S6Uu5a8RHzmq4Uvts+hKMZaxFQ3wOXP9S5++XlM0Tq+IPuKzBvkLtt6ixGf22PHd896jamvwXR/Cg 213fCApPqBT4Yg65MX0lo7Xu0XJF1kUIABv5wE4Lh4AVUnY+9lOazph6omWQMLfeXjReWGLD25Ebk N/GIrH8iISB1uirw=; Received: from szxga06-in.huawei.com ([45.249.212.32] helo=huawei.com) by sfi-mx-3.v28.lw.sourceforge.com with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.90_1) id 1huXIM-00BJz7-GR for linux-f2fs-devel@lists.sourceforge.net; Mon, 05 Aug 2019 07:20:40 +0000 Received: from DGGEMS405-HUB.china.huawei.com (unknown [172.30.72.59]) by Forcepoint Email with ESMTP id C9479E04882FA6FD9799; Mon, 5 Aug 2019 15:20:31 +0800 (CST) Received: from huawei.com (10.90.53.225) by DGGEMS405-HUB.china.huawei.com (10.3.19.205) with Microsoft SMTP Server id 14.3.439.0; Mon, 5 Aug 2019 15:20:25 +0800 From: Lihong Kou To: , Date: Mon, 5 Aug 2019 15:26:21 +0800 Message-ID: <1564989981-104324-1-git-send-email-koulihong@huawei.com> X-Mailer: git-send-email 2.7.4 MIME-Version: 1.0 X-Originating-IP: [10.90.53.225] X-CFilter-Loop: Reflected X-Headers-End: 1huXIM-00BJz7-GR Subject: [f2fs-dev] [PATCH] fsck.f2fs: fix the bug in reserve_new_block X-BeenThere: linux-f2fs-devel@lists.sourceforge.net X-Mailman-Version: 2.1.21 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, fangwei1@huawei.com, linux-f2fs-devel@lists.sourceforge.net Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: linux-f2fs-devel-bounces@lists.sourceforge.net 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 --- 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 _______________________________________________ Linux-f2fs-devel mailing list Linux-f2fs-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel