Re: [PATCH v4 8/9] NFSD: Prevent client use-after-free during close_lru reaping
Jeff Layton <[email protected]>
| Newsgroups | gmane.linux.nfs |
|---|---|
| Message-ID | <[email protected]> |
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 <[email protected]>
> ---
> 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(<, 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 <[email protected]>