Received: by 2002:a05:6359:c8b:b0:c7:702f:21d4 with SMTP id go11csp3547857rwb; Tue, 20 Sep 2022 00:57:15 -0700 (PDT) X-Google-Smtp-Source: AMsMyM5uVnJsQ5xDJz3mH1Q6DG3QRjUxtZcCTg3SoPC2uzrt/fpI3QvDAQtRPvp0xgW9wNvKtUzi X-Received: by 2002:a17:907:74e:b0:74f:83d4:cf58 with SMTP id xc14-20020a170907074e00b0074f83d4cf58mr16202132ejb.178.1663660635664; Tue, 20 Sep 2022 00:57:15 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1663660635; cv=none; d=google.com; s=arc-20160816; b=f7X+n7RCJZIg4qkwBDbslW3aOYRqKab3D36TymKeuOHztmWxIE97Finv5N5L/VtXgd tn0jcmtZ0LfaDWmcX2kYVVHzwN+ikDWAsdsr/kHz8/541X+N/x2ZYVQ+afCeMTqeI/bL cyZDCBKpT3OK6No5AjpcjoDBVmJ0HNEtO3L6U9YQAb/Ig7/ae+ijz9nbxv+zoWeJ11yk ths6nOAlGw5bLJjblO5yZGMTwuqww6Ra0NtG6L0e8m0dkCPhDnLpWaa8/2Wt65HA9fB0 pmqwTPi4uMsGp4jGgHshiv17heB7lAPnL6bMClqKYjgfNOhErQLnFHYp66BsOfXURHtn iZHw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:abuse-reports-to:tuid:mime-version:message-id :date:subject:cc:to:from; bh=oqoAXVsCP3I6aOQyuEbVnsfcJpaAgchqRAkgTs5goG8=; b=j/HCYlm3EIFl25Gz7CxQTTXI3PX5WtUzbw3VFK9BI4g04lrcuThaQU6yl5haxqyXgh jx7KhUVX//z92yDaOdhD5fSm14fCzzQ2Nh/4S7pnXYbDuUERBMcYC8sBfDunyJmoNtiz jQBamWdKTzHYYYYbK4Nnf4IuP5M++ycvEixNi4ugevyGh2A38gCJbtDergKk9aeUxHkG HSYa/wbp95ymIYfGTm6Ql4AaMHDt7MfaR69wtp/nuT2l2kdChnoHAmIOU2iJZQEXPOfX VYQRxjSmYceKT8075hghQQ4N4SBwyRswQrfvq8R5FasSjtMAI20yHbyZsb9F+p5t21OB X9cQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id s7-20020a508d07000000b0045194b3d3e3si1053962eds.555.2022.09.20.00.56.50; Tue, 20 Sep 2022 00:57:15 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230214AbiITHhZ (ORCPT + 99 others); Tue, 20 Sep 2022 03:37:25 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:45020 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230220AbiITHhW (ORCPT ); Tue, 20 Sep 2022 03:37:22 -0400 Received: from ssh248.corpemail.net (ssh248.corpemail.net [210.51.61.248]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 0B09760683 for ; Tue, 20 Sep 2022 00:37:19 -0700 (PDT) Received: from ([60.208.111.195]) by ssh248.corpemail.net ((D)) with ASMTP (SSL) id OGF00011; Tue, 20 Sep 2022 15:37:11 +0800 Received: from lihongweizz00.home.langchao.com (10.180.204.84) by jtjnmail201605.home.langchao.com (10.100.2.5) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.12; Tue, 20 Sep 2022 15:37:15 +0800 From: Rock Li To: , , CC: , , Rock Li Subject: [PATCH] ocfs2: fix crash issue if access released lockres in debugfs Date: Tue, 20 Sep 2022 15:36:38 +0800 Message-ID: <20220920073638.1358-1-lihongweizz@inspur.com> X-Mailer: git-send-email 2.17.1 MIME-Version: 1.0 Content-Type: text/plain X-Originating-IP: [10.180.204.84] X-ClientProxiedBy: Jtjnmail201614.home.langchao.com (10.100.2.14) To jtjnmail201605.home.langchao.com (10.100.2.5) tUid: 2022920153711997fac9f361039e13e098431dd3977e6 X-Abuse-Reports-To: service@corp-email.com Abuse-Reports-To: service@corp-email.com X-Complaints-To: service@corp-email.com X-Report-Abuse-To: service@corp-email.com X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,SPF_HELO_NONE, SPF_PASS autolearn=ham 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 Access locking_state of dlm debugfs may cause crash as scene below: Proc A: Proc that access debuginfo: add_lockres_tracking(lockresA) ... ocfs2_dlm_seq_next(): //priv->p_iter_res points to next //lockres e.g. B. priv->p_tmp_res hold //copy of lockres A before leave ocfs2_dlm_seq_show() ... remove_lockres_tracking(lockres B): //free lockres B, l_debug_list in //priv->p_ter_res is updated but not //priv->p_tmp_res ... ocfs2_dlm_seq_next(): //priv->p_tmp_res which holds a old copy of //lockres A, the l_debug_list holds a //out-of-date succeed pointer, which will //cause crash as //access invalid memory iter = v; //priv->p_tmp_res iter = ocfs2_dlm_next_res(iter, priv) The root cause of this issue is that private->p_iter_res acts as the agent of accessing lockres and is protected by ocfs2_dlm_tracking_lock while p_tmp_res is only a copy of the lockres and will be out-of-dated after leave critial region of ocfs2_dlm_tracking_lock. We should use priv->p_ter_res as the forward iterater instead. Signed-off-by: Rock Li --- fs/ocfs2/dlmglue.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/fs/ocfs2/dlmglue.c b/fs/ocfs2/dlmglue.c index c28bc98..5d84350 100644 --- a/fs/ocfs2/dlmglue.c +++ b/fs/ocfs2/dlmglue.c @@ -3109,7 +3109,7 @@ static void *ocfs2_dlm_seq_next(struct seq_file *m, void *v, loff_t *pos) struct ocfs2_lock_res *dummy = &priv->p_iter_res; spin_lock(&ocfs2_dlm_tracking_lock); - iter = ocfs2_dlm_next_res(iter, priv); + iter = ocfs2_dlm_next_res(dummy, priv); list_del_init(&dummy->l_debug_list); if (iter) { list_add(&dummy->l_debug_list, &iter->l_debug_list); -- 1.8.3.1