Received: by 2002:a5d:9c59:0:0:0:0:0 with SMTP id 25csp2283172iof; Wed, 8 Jun 2022 01:22:29 -0700 (PDT) X-Google-Smtp-Source: ABdhPJyYVeYDFp2DOWSgAALlm6mwNd5BWrHHs+GD5QuDLdEj66MjQ2lF+GTgWCpZVwguGlAxPsfG X-Received: by 2002:a05:6a00:1a91:b0:51c:2ef4:fa1c with SMTP id e17-20020a056a001a9100b0051c2ef4fa1cmr10249180pfv.75.1654676549156; Wed, 08 Jun 2022 01:22:29 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1654676549; cv=none; d=google.com; s=arc-20160816; b=E8JAgqYYq7XGTNe+xWvb0zMlIRJXcRUOlgx6pyXEKarCvrGTrGCoadtcWhASqw8+ep Dkxyvj4lNvDk/tbHY/rm+SRR2lVdQM4+ooLOV1uHQj9t6jhfiFHxmZ4d4kUvzsnWNPKq lsRG5X0SqidIRuGeLrm5uqd21/lRItZMXhbN40wD12Eq6eunA+068tZhT35sm9V0rZg/ qa0xl5APoWgikQUdR7kCzsOzks94Am1C577Eb3g9/fKybTDB9yaqC3Wbpri5+yZeQbke ZVOsTrBlkEA0+lgbhzjrgQ4BcUCfsf0u5bNkP7YA7ViA4yvH4ItmlYgy1q6Md3p5OI10 8VYw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :user-agent:references:in-reply-to:message-id:date:subject:cc:to :from:dkim-signature; bh=6j5W4KokySL0MqHk/7//2rSWg2ilF9zacOR3w43WFR0=; b=aC6+UQZZ/IzVSOX+NrADdBNnStJBBgjP+urUZwwynMPX4FpevAD3qfx2BNNVDCIx/T DC2NP1HAxaEShKjvPH+S5+Wwzcwq7Af4+adYiFzr2zh+vHMKSzbAjTSS8capYiz4fDH4 r/MZG9R4z0W21nSZ8nzKHJBGLTCj70UM4zmO2sNqitVb3NDhMAqB8veoim4CQvcGJS+c Vi0FiozmB0RL/1cf0cLctnB9gYWhQ76a2tezlVqpLMkCQkNXcY4H2FBfBW7/tOs3u7I0 dh6/Xrpl5KRI9tZ7HM+H2keNM2dhs2zBfGSQfn2JswoaeA2/x6hVo/7fIt3JQmEFteHH 8YNA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b=QGEBgJFU; spf=softfail (google.com: domain of transitioning linux-kernel-owner@vger.kernel.org does not designate 23.128.96.19 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linuxfoundation.org Return-Path: Received: from lindbergh.monkeyblade.net (lindbergh.monkeyblade.net. [23.128.96.19]) by mx.google.com with ESMTPS id s129-20020a632c87000000b003f5e622a6a0si19450701pgs.690.2022.06.08.01.22.28 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 08 Jun 2022 01:22:29 -0700 (PDT) Received-SPF: softfail (google.com: domain of transitioning linux-kernel-owner@vger.kernel.org does not designate 23.128.96.19 as permitted sender) client-ip=23.128.96.19; Authentication-Results: mx.google.com; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b=QGEBgJFU; spf=softfail (google.com: domain of transitioning linux-kernel-owner@vger.kernel.org does not designate 23.128.96.19 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linuxfoundation.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id EA8A01CEAF7; Wed, 8 Jun 2022 00:52:46 -0700 (PDT) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1356738AbiFHCOx (ORCPT + 99 others); Tue, 7 Jun 2022 22:14:53 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:50338 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231328AbiFHBWu (ORCPT ); Tue, 7 Jun 2022 21:22:50 -0400 Received: from dfw.source.kernel.org (dfw.source.kernel.org [IPv6:2604:1380:4641:c500::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id A4AEC1957B6; Tue, 7 Jun 2022 12:18:15 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id 7BE3961976; Tue, 7 Jun 2022 19:18:14 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 89A80C34115; Tue, 7 Jun 2022 19:18:13 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1654629493; bh=ZarOxv6OC6Lb7v0F8skjQkznp1Vq8KrFhn6FrSySwWs=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=QGEBgJFUsqbipf/tCn/IpzP3HlBfKEunEBlY3Gz88iEvbTzdHB8xVB83OCC2LaMPp zbE+7Z8zu1bz8apvB+tLXsy6q/uhe9VgAvsoPJxmOpINjQggasFk1R66bfY9WhkGCm 0Qgc4O4ylbZMFPCslNraHVXOYj+MdUbPNUi4Ptb4= From: Greg Kroah-Hartman To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman , stable@vger.kernel.org, Ming Yan , Chao Yu , Jaegeuk Kim Subject: [PATCH 5.18 710/879] f2fs: fix to clear dirty inode in f2fs_evict_inode() Date: Tue, 7 Jun 2022 19:03:48 +0200 Message-Id: <20220607165023.462494488@linuxfoundation.org> X-Mailer: git-send-email 2.36.1 In-Reply-To: <20220607165002.659942637@linuxfoundation.org> References: <20220607165002.659942637@linuxfoundation.org> User-Agent: quilt/0.66 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-3.1 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,RDNS_NONE,SPF_HELO_NONE,T_SCC_BODY_TEXT_LINE autolearn=unavailable autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Chao Yu commit f2db71053dc0409fae785096ad19cce4c8a95af7 upstream. As Yanming reported in bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=215904 The kernel message is shown below: kernel BUG at fs/f2fs/inode.c:825! Call Trace: evict+0x282/0x4e0 __dentry_kill+0x2b2/0x4d0 shrink_dentry_list+0x17c/0x4f0 shrink_dcache_parent+0x143/0x1e0 do_one_tree+0x9/0x30 shrink_dcache_for_umount+0x51/0x120 generic_shutdown_super+0x5c/0x3a0 kill_block_super+0x90/0xd0 kill_f2fs_super+0x225/0x310 deactivate_locked_super+0x78/0xc0 cleanup_mnt+0x2b7/0x480 task_work_run+0xc8/0x150 exit_to_user_mode_prepare+0x14a/0x150 syscall_exit_to_user_mode+0x1d/0x40 do_syscall_64+0x48/0x90 The root cause is: inode node and dnode node share the same nid, so during f2fs_evict_inode(), dnode node truncation will invalidate its NAT entry, so when truncating inode node, it fails due to invalid NAT entry, result in inode is still marked as dirty, fix this issue by clearing dirty for inode and setting SBI_NEED_FSCK flag in filesystem. output from dump.f2fs: [print_node_info: 354] Node ID [0xf:15] is inode i_nid[0] [0x f : 15] Cc: stable@vger.kernel.org Reported-by: Ming Yan Signed-off-by: Chao Yu Signed-off-by: Jaegeuk Kim Signed-off-by: Greg Kroah-Hartman --- fs/f2fs/inode.c | 16 +++++++++++++++- 1 file changed, 15 insertions(+), 1 deletion(-) --- a/fs/f2fs/inode.c +++ b/fs/f2fs/inode.c @@ -796,8 +796,22 @@ retry: f2fs_lock_op(sbi); err = f2fs_remove_inode_page(inode); f2fs_unlock_op(sbi); - if (err == -ENOENT) + if (err == -ENOENT) { err = 0; + + /* + * in fuzzed image, another node may has the same + * block address as inode's, if it was truncated + * previously, truncation of inode node will fail. + */ + if (is_inode_flag_set(inode, FI_DIRTY_INODE)) { + f2fs_warn(F2FS_I_SB(inode), + "f2fs_evict_inode: inconsistent node id, ino:%lu", + inode->i_ino); + f2fs_inode_synced(inode); + set_sbi_flag(sbi, SBI_NEED_FSCK); + } + } } /* give more chances, if ENOMEM case */