Received: from smtp.kernel.org (aws-us-west-2-korg-mail-alma10-1.taild15c8.ts.net [100.103.45.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id AE7541DB92C for ; Mon, 7 Sep 2026 20:18:47 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=100.103.45.18 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1788812329; cv=none; b=r7DYyoZZ77dMb5G7UUDhAmnOBLcJW5xSwrC3Z3MZhp2ho1aPPwxCfykhCltzAWdAnue9u+7cG4p0HBaE99IHGYecPubTnaKD6mplbs3TowPlOYS1ZaHxqWmONgFK0OhZIIwdnMlzCL5TOWYogkRGRYnwY8Fa3WPfCmBvdMPiWwo= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1788812329; c=relaxed/simple; bh=C+h1EOvzykwWgty1dC0/n1pI77B3AMG27hzUFrpAzFo=; h=From:To:Cc:Subject:Date:Message-ID:In-Reply-To:References: MIME-Version; b=sfr87lgdhp9qS0n0JMvThjJPxvA2GlOZUvgiO+H2uYSQJuPjRUdjifZWmawDShV3o3jX1CB5jRsmRH368pbD4W/bIloy5Y+nFcIEXhxxp/dmU1rDTDMqYJwFsbezxXGfb/ZSN63VRwsBEr0zYLcTJZAkagVdfc3NZWVSZG2hwC0= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=Y9yIp5+3; arc=none smtp.client-ip=100.103.45.18 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="Y9yIp5+3" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 0B8191F00A3F; Mon, 7 Sep 2026 20:18:46 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org; s=k20260515; t=1788812327; bh=AHTjwxlRmk4WbaTF/mxJpsg+gDAwm0DMzCtwExM+1uo=; h=From:To:Cc:Subject:Date:In-Reply-To:References; b=Y9yIp5+3JPp7rSS+cr4gN9IsFzE9RZM+yu6JaglTZZgRmVmeRzW7m5c6ufz/RYguT LTLX8hdXUIAE49z4UORoj5yiBAjAfULfAnetauUYhQMmq9FY16FAtQfwIIgEWUiPc0 tsvUbNWxDICUg51rWuYSxbV/BkguacE03NeqiCbSmRtnpjIeubfr3M0qvGWb/gjKZC yZ5sxhCaUrKgTu720D9LLjFjqXJUR5uKrgbesX7F3vjO4VXnwmYXGk+E7MGPhpGLqD Qlj4b59FHDGJHKazBP7ojXl8VvXYZp8F8lXI/hkZm4L4AY2W3anDSP3/EHS6CzQCKI 3p5pMLwv+2EJw== From: Sasha Levin To: stable@vger.kernel.org Cc: Chuck Lever , NeilBrown , Jeff Layton , Sasha Levin Subject: [PATCH 7.2.y 2/6] NFSD: Prevent client use-after-free during admin state revocation Date: Mon, 7 Sep 2026 16:18:40 -0400 Message-ID: <20260907201844.381343-2-sashal@kernel.org> X-Mailer: git-send-email 2.53.0 In-Reply-To: <20260907201844.381343-1-sashal@kernel.org> References: <2026090304-open-erasable-9a07@gregkh> <20260907201844.381343-1-sashal@kernel.org> Precedence: bulk X-Mailing-List: stable@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Transfer-Encoding: 8bit From: Chuck Lever [ Upstream commit e270e5a0778e5bff852c8862ce9576ce70359393 ] A stateid holds only a bare pointer to its nfs4_client; a stateid reference does not pin it. The client survives only because __destroy_client() drains its stateids before free_client() runs. nfsd4_revoke_states() drops nn->client_lock across revoke_one_stid(), which dereferences the client to revoke a stateid and read clp->cl_minorversion. A teardown racing the dropped lock can free the client first. Pinning cl_rpc_users under client_lock blocks the DESTROY_CLIENTID and EXCHANGE_ID teardown, which refuses while cl_rpc_users is non-zero. force_expire_client() ignores it: once its wait for cl_rpc_users to reach zero has passed, a later pin goes unnoticed. Under client_lock, skip a client whose cl_time is already zero -- force_expire_client() clears it there before waiting -- otherwise pin cl_rpc_users before dropping the lock. The walk then either sees the expiry and skips, or pins in time for that wait to cover the revoke. Fixes: 1c13bf9f2e3c ("nfsd: allow lock state ids to be revoked and then freed") Cc: stable@vger.kernel.org Reviewed-by: NeilBrown Reviewed-by: Jeff Layton Link: https://patch.msgid.link/20260709-cel-v4-3-1d519d9be0cb@kernel.org Signed-off-by: Chuck Lever Stable-dep-of: 2330b788d732 ("NFSD: Prevent client use-after-free during close_lru reaping") Signed-off-by: Sasha Levin --- fs/nfsd/nfs4state.c | 22 ++++++++++++++++++++-- 1 file changed, 20 insertions(+), 2 deletions(-) diff --git a/fs/nfsd/nfs4state.c b/fs/nfsd/nfs4state.c index e1a8d300636b9..8b0feceee5ac6 100644 --- a/fs/nfsd/nfs4state.c +++ b/fs/nfsd/nfs4state.c @@ -1889,9 +1889,19 @@ void nfsd4_revoke_states(struct nfsd_net *nn, struct super_block *sb) struct nfs4_client *clp; retry: list_for_each_entry(clp, head, cl_idhash) { - struct nfs4_stid *stid = find_one_sb_stid(clp, sb, - sc_types); + struct nfs4_stid *stid; + + /* + * force_expire_client() ignores cl_rpc_users once + * its wait_event() has passed, so pinning cannot + * keep an already-expiring client alive; the + * expiry path revokes its states instead. + */ + if (is_client_expired(clp)) + continue; + stid = find_one_sb_stid(clp, sb, sc_types); if (stid) { + atomic_inc(&clp->cl_rpc_users); spin_unlock(&nn->client_lock); revoke_one_stid(nn, clp, stid); nfs4_put_stid(stid); @@ -1904,6 +1914,9 @@ void nfsd4_revoke_states(struct nfsd_net *nn, struct super_block *sb) */ nn->nfs40_last_revoke = ktime_get_boottime_seconds(); + if (atomic_dec_and_test(&clp->cl_rpc_users) && + is_client_expired(clp)) + wake_up_all(&expiry_wq); goto retry; } } @@ -3259,6 +3272,11 @@ static void force_expire_client(struct nfs4_client *clp) trace_nfsd_clid_admin_expired(&clp->cl_clientid); + /* + * cl_time is cleared under client_lock before the wait so a + * revocation walk pinning cl_rpc_users under it either skips + * this client or is seen by this wait_event(). + */ spin_lock(&nn->client_lock); clp->cl_time = 0; spin_unlock(&nn->client_lock); -- 2.53.0