Received-SPF: pass (google.com: domain of linux-nfs+bounces-1727-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:40f1:3f00::1 as permitted sender) client-ip=2604:1380:40f1:3f00::1;
Subject: [PATCH v2 0/4] RELEASE_LOCKOWNER fixes for v5.15.y
From: Chuck Lever <cel@kernel.org>
To: neilb@suse.de
Cc: linux-nfs@vger.kernel.org
Date: Fri, 02 Feb 2024 22:55:14 -0500
Message-ID: 
 <170693220850.20619.2532987152854323295.stgit@klimt.1015granger.net>
User-Agent: StGit/1.5
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit

Hi Neil -

Series updated to include "nfsd4: add refcount for
nfsd4_blocked_lock". "nfsd: don't call locks_release_private() twice
concurrently" will be applied automatically when it is subsequently
merged in v6.9.

Test server kernel was built with KASAN enabled. The series passes
pynfs, (x)fstests on NFSv4.0, and the git regression suite on
NFSv4.0 with no crashes, KASAN splats, or memory leaks detected.

---

Chuck Lever (2):
      NFSD: Modernize nfsd4_release_lockowner()
      NFSD: Add documenting comment for nfsd4_release_lockowner()

NeilBrown (1):
      nfsd: fix RELEASE_LOCKOWNER

Vasily Averin (1):
      nfsd4: add refcount for nfsd4_blocked_lock


 fs/nfsd/nfs4state.c | 90 +++++++++++++++++++++++++++++----------------
 fs/nfsd/state.h     |  1 +
 2 files changed, 59 insertions(+), 32 deletions(-)

--
Chuck Lever