Received: by 2002:a05:6a11:4021:0:0:0:0 with SMTP id ky33csp1540135pxb; Thu, 16 Sep 2021 09:31:30 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxZJeq9ttWCpxApt0MLK0Sl1oah301p7WoV0zIWGkdCFO3LM+UzXfJh141zw/cXw2g4QuVf X-Received: by 2002:a17:906:a59:: with SMTP id x25mr7047848ejf.33.1631809890702; Thu, 16 Sep 2021 09:31:30 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1631809890; cv=none; d=google.com; s=arc-20160816; b=cIXOFrIsJQdd700h/JPlbBiR2vQxRqOc43e0579pzt/sARJr4Gzjtaic60WGEwl4LA aUZmZ5quxBcUTPE9zNDk0Bg8phAKm/R98C4ka36kAAo+TJeZNjUqlXbnhEygFXE4lw55 kBV9iYHx5fJU5nvcRnnqjb2QNMpJ7feJOJSWEIOdYIiVxo7wdap5TLQExuwcv+vOEWh+ hfVDpvbkw+FB0csyFq8erB4tqef7XzPTPjiOU4L12EbEhV91WKmUSGOGNjanlsefPD67 f9X/oJDP84p0XSxtUliiC3dUcawwaJU3t5N4HsyaZu+Y+m7lfN8j1TiZSqzBxyej5j+1 NK6w== 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=4LcM2k1BZCMhorrbyvUwwajroHbnWNv9GQhBzXRPIQM=; b=SmsrKg1qSWuxB77lAJCWoLlpeo9wZ1HXpyWRtpIRFJfzgHeG4b8Ln9L3FLFouYItpY Xy7zsKDTRkW5+8FD+ilBpxMrdS9imtUFfagDDEXNFaXhGJ9HITzbsC2swBb0Zy+zWZeh L8oBy3IGhMAaVnPnJjPWRWQIRfxzkmsBe8YeKDK9Bzs8uxeSAVuyBFEkXN5c48qsg0fx 7PckzvaJbzqi25mYDD4wRia98JrWlkvqxH6Gkw8k+HwSHqa76L4BpG4b2BZCpVgeyRX6 jE7IV8WAsmCKe5TC0FtuUmIrcnSRA4n8GayF34vDR49K/Fv6RHDXUP8qX3cyxvRnWStV fECQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b=L5MxjZmR; 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 bi20si3812002ejb.575.2021.09.16.09.31.00; Thu, 16 Sep 2021 09:31:30 -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=L5MxjZmR; 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 S241558AbhIPQ1Y (ORCPT + 99 others); Thu, 16 Sep 2021 12:27:24 -0400 Received: from mail.kernel.org ([198.145.29.99]:55230 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S241476AbhIPQTi (ORCPT ); Thu, 16 Sep 2021 12:19:38 -0400 Received: by mail.kernel.org (Postfix) with ESMTPSA id CA2776137D; Thu, 16 Sep 2021 16:13:34 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1631808815; bh=+fvd5OzYrWN5OOWbb3QENra4Vd4JtouksqyN195Z6wA=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=L5MxjZmRdZH+Y2LvdoE4VeabLcbpsJR9ENL1tf37WV5yceK1TCT31buMxk15qtps0 7mEm/iE6qlB8s87Q249rkamgeMXTP61v+W8pUGsmGf6ITFewmjgzatCosbKMvRt5ip oBV/Qs+NgyxE0oKNg/lRA8Jcx0RvarzQxyWv5RHc= From: Greg Kroah-Hartman To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman , stable@vger.kernel.org, Bob Peterson , Sasha Levin Subject: [PATCH 5.10 232/306] gfs2: Dont call dlm after protocol is unmounted Date: Thu, 16 Sep 2021 17:59:37 +0200 Message-Id: <20210916155801.959951707@linuxfoundation.org> X-Mailer: git-send-email 2.33.0 In-Reply-To: <20210916155753.903069397@linuxfoundation.org> References: <20210916155753.903069397@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 153272f82984..5564aa8b4592 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