Linux NFS development
 help / color / mirror / Atom feed
From: Jeff Layton <jlayton@kernel.org>
To: Chuck Lever <cel@kernel.org>, NeilBrown <neil@brown.name>,
	Olga Kornievskaia <okorniev@redhat.com>,
	Dai Ngo <Dai.Ngo@oracle.com>, Tom Talpey <tom@talpey.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: [PATCH v4 8/9] NFSD: Prevent client use-after-free during close_lru reaping
Date: Thu, 09 Jul 2026 14:37:23 -0400	[thread overview]
Message-ID: <ada73c77322ddc803836c42699478d27ed49dcf6.camel@kernel.org> (raw)
In-Reply-To: <20260709-cel-v4-8-1d519d9be0cb@kernel.org>

On Thu, 2026-07-09 at 13:40 -0400, Chuck Lever wrote:
> An nfs4_openowner left on nn->close_lru after its final CLOSE keeps
> its last closed stateid in oo_last_closed_stid, holding only a raw
> pointer to its nfs4_client. The laundromat reaps timed-out entries,
> drops nn->client_lock, and calls nfs4_put_stid(), which dereferences
> the client through cl_lock. Nothing pins the client across that
> window, so a concurrent force_expire_client() can free it and
> nfs4_put_stid() reads freed memory. __destroy_client() hits the same
> race, walking clp->cl_openowners without cl_lock.
> 
> Pin the client with cl_rpc_users before dropping client_lock, and
> skip clients already expiring. __destroy_client() then cleans up its
> own close_lru entries through release_last_closed_stateid(), so
> teardown no longer races the laundromat.
> 
> Fixes: 217526e7ecc9 ("nfsd: protect the close_lru list and oo_last_closed_stid with client_lock")
> Signed-off-by: Chuck Lever <cel@kernel.org>
> ---
>  fs/nfsd/nfs4state.c | 5 +++++
>  1 file changed, 5 insertions(+)
> 
> diff --git a/fs/nfsd/nfs4state.c b/fs/nfsd/nfs4state.c
> index 4acd02f1642c..20556b8f186a 100644
> --- a/fs/nfsd/nfs4state.c
> +++ b/fs/nfsd/nfs4state.c
> @@ -7581,11 +7581,16 @@ nfs4_laundromat(struct nfsd_net *nn)
>  		if (!state_expired(&lt, oo->oo_time))
>  			break;
>  		list_del_init(&oo->oo_close_lru);
> +		clp = oo->oo_owner.so_client;
> +		if (is_client_expired(clp))
> +			continue;
>  		stp = oo->oo_last_closed_stid;
>  		oo->oo_last_closed_stid = NULL;
> +		atomic_inc(&clp->cl_rpc_users);
>  		spin_unlock(&nn->client_lock);
>  		nfs4_put_stid(&stp->st_stid);
>  		spin_lock(&nn->client_lock);
> +		put_client_no_renew_locked(clp);
>  	}
>  	spin_unlock(&nn->client_lock);
>  

Reviewed-by: Jeff Layton <jlayton@kernel.org>

  reply	other threads:[~2026-07-09 18:37 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-09 17:40 [PATCH v4 0/9] NFSD: Fix UAFs in client teardown and state revocation Chuck Lever
2026-07-09 17:40 ` [PATCH v4 1/9] NFSD: Prevent lock owner use-after-free during client teardown Chuck Lever
2026-07-09 17:40 ` [PATCH v4 2/9] NFSD: Prevent client use-after-free during delegation revoke Chuck Lever
2026-07-09 17:40 ` [PATCH v4 3/9] NFSD: Prevent client use-after-free during admin state revocation Chuck Lever
2026-07-09 17:40 ` [PATCH v4 4/9] NFSD: Prevent client use-after-free during export " Chuck Lever
2026-07-09 17:40 ` [PATCH v4 5/9] NFSD: Prevent client use-after-free during NFSv4.0 revoked-state cleanup Chuck Lever
2026-07-09 17:40 ` [PATCH v4 6/9] NFSD: Consolidate the revocation-path client unpin Chuck Lever
2026-07-09 17:40 ` [PATCH v4 7/9] NFSD: Prevent client use-after-free during blocked-lock reaping Chuck Lever
2026-07-09 18:36   ` Jeff Layton
2026-07-09 17:40 ` [PATCH v4 8/9] NFSD: Prevent client use-after-free during close_lru reaping Chuck Lever
2026-07-09 18:37   ` Jeff Layton [this message]
2026-07-09 17:40 ` [PATCH v4 9/9] NFSD: Release the export reference when reaping open stateids Chuck Lever
2026-07-09 18:40   ` Jeff Layton
2026-07-09 19:55     ` Chuck Lever

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ada73c77322ddc803836c42699478d27ed49dcf6.camel@kernel.org \
    --to=jlayton@kernel.org \
    --cc=Dai.Ngo@oracle.com \
    --cc=cel@kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=neil@brown.name \
    --cc=okorniev@redhat.com \
    --cc=tom@talpey.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox