Received: by 2002:a05:6a11:4021:0:0:0:0 with SMTP id ky33csp2319416pxb; Mon, 20 Sep 2021 18:42:30 -0700 (PDT) X-Google-Smtp-Source: ABdhPJyiIOHCFav8XMzLMHE76ivF0RvsRDcuUe9qD4uzbTvdjbttfl96RZQPu9F2HnCNHLdh2wR6 X-Received: by 2002:a92:90c:: with SMTP id y12mr19912349ilg.276.1632188549990; Mon, 20 Sep 2021 18:42:29 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1632188549; cv=none; d=google.com; s=arc-20160816; b=h7MQytyJxpkC8YFD+0j9K86NB/fkc8LciFYvyg/HouI8t9ci7lzskQHwEOUqaNqPY6 FBDIpU9gX3j/f837WMicPiBfDb8StinpeFd512Hcx2C+gwBWwv63bzIkugfQbkpY9uei vgleX2Rw7cqgb1vpK0rALY6h5H9kjHyxOFDBnt4AnkIWaLq2wpvbEfBHODkrpchl9hZL zX3MKMFuUKwvXTi+5XfkeqBEnY1cPVQa6TOqDpvsqJUaZ4fgNGHsAACJN/3iH7YBsiIa TNwO/f8wRpf5wKJfm/YXU4o22UeQcK5kfrNwZcL4mweTcg4HkvKm0H4RuAjVwA/fQHkq WlEg== 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=eZDdVX7iF93wNTo40DYII8v7n5LGWTpFY+iawqa1BnM=; b=B6IFyLolHC+7ORKwoAafIGa8YEIH6kxNmvwMYWbJVRQ0+ADxJWaHA1NsR6V2e4KNb8 /xLJbHRYY/ovcmvp6KhlKbAyDHu47FGynD8mWVcY0mjwXOYetguymtM8S7K1nw4kgUZm 4shhey5MRMSJRD7mtYGBC4Dbk8AmRAzvWOyHT1ZaeCliN0D48EX2SiW1APUZke6M29xZ ji9gmqAeMaHuoQiGi9pJfJW/J5VDrOIjNKurHf2a/DQ7LXisNDAkJFaU/kKfCOChcQIg kNqSbeZO7WlZd1sdVKfVsfPoxH2shvqgCq4YBulKLr94ZA7I0G8xK6xry/XuZq7j6njm w+EQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b=TsAumL49; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 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 vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id o16si12757965ilh.153.2021.09.20.18.42.19; Mon, 20 Sep 2021 18:42:29 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b=TsAumL49; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linuxfoundation.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S245582AbhITQyf (ORCPT + 99 others); Mon, 20 Sep 2021 12:54:35 -0400 Received: from mail.kernel.org ([198.145.29.99]:37262 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230095AbhITQuo (ORCPT ); Mon, 20 Sep 2021 12:50:44 -0400 Received: by mail.kernel.org (Postfix) with ESMTPSA id 6909C61355; Mon, 20 Sep 2021 16:49:07 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1632156547; bh=tZ4XmEDq5WrOAOAVUR7U8zB9+XCNdK20ihOrupYXedc=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=TsAumL49t9+uAGIN6sToYm4mFFLaR7q9rc0X/42TtTLiqTCq9924qxIphXKADOofe f+uaoDgM0Lqm1QcroiVw41sMhbZUfNKcHh/mTbW4fSN1afBvbw00OSJ7BU+B9cB5Zm 8xpLwxCUTNmmWCPPo9l1uqkvzybAtIy/QvqmrtJ4= From: Greg Kroah-Hartman To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman , stable@vger.kernel.org, Bob Peterson , Sasha Levin Subject: [PATCH 4.4 109/133] gfs2: Dont call dlm after protocol is unmounted Date: Mon, 20 Sep 2021 18:43:07 +0200 Message-Id: <20210920163916.188583062@linuxfoundation.org> X-Mailer: git-send-email 2.33.0 In-Reply-To: <20210920163912.603434365@linuxfoundation.org> References: <20210920163912.603434365@linuxfoundation.org> User-Agent: quilt/0.66 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Bob Peterson [ Upstream commit d1340f80f0b8066321b499a376780da00560e857 ] In the gfs2 withdraw sequence, the dlm protocol is unmounted with a call to lm_unmount. After a withdraw, users are allowed to unmount the withdrawn file system. But at that point we may still have glocks left over that we need to free via unmount's call to gfs2_gl_hash_clear. These glocks may have never been completed because of whatever problem caused the withdraw (IO errors or whatever). Before this patch, function gdlm_put_lock would still try to call into dlm to unlock these leftover glocks, which resulted in dlm returning -EINVAL because the lock space was abandoned. These glocks were never freed because there was no mechanism after that to free them. This patch adds a check to gdlm_put_lock to see if the locking protocol was inactive (DFL_UNMOUNT flag) and if so, free the glock and not make the invalid call into dlm. I could have combined this "if" with the one that follows, related to leftover glock LVBs, but I felt the code was more readable with its own if clause. Signed-off-by: Bob Peterson Signed-off-by: Sasha Levin --- fs/gfs2/lock_dlm.c | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/fs/gfs2/lock_dlm.c b/fs/gfs2/lock_dlm.c index 3cbc9147286d..da9f97911852 100644 --- a/fs/gfs2/lock_dlm.c +++ b/fs/gfs2/lock_dlm.c @@ -296,6 +296,11 @@ static void gdlm_put_lock(struct gfs2_glock *gl) gfs2_sbstats_inc(gl, GFS2_LKS_DCOUNT); gfs2_update_request_times(gl); + /* don't want to call dlm if we've unmounted the lock protocol */ + if (test_bit(DFL_UNMOUNT, &ls->ls_recover_flags)) { + gfs2_glock_free(gl); + return; + } /* don't want to skip dlm_unlock writing the lvb when lock has one */ if (test_bit(SDF_SKIP_DLM_UNLOCK, &sdp->sd_flags) && -- 2.30.2