public inbox for linux-nfs@vger.kernel.org
 help / color / mirror / Atom feed
From: bfields@fieldses.org (J. Bruce Fields)
To: "J. Bruce Fields" <bfields@redhat.com>
Cc: Trond Myklebust <trondmy@hammerspace.com>,
	Anna Schumaker <schumakeranna@gmail.com>,
	linux-nfs@vger.kernel.org
Subject: Re: [PATCH] SUNRPC: 'Directory with parent 'rpc_clnt' already present!'
Date: Wed, 13 May 2020 18:40:33 -0400	[thread overview]
Message-ID: <20200513224033.GA1415@fieldses.org> (raw)
In-Reply-To: <1589409520-1344-1-git-send-email-bfields@redhat.com>

On Wed, May 13, 2020 at 06:38:40PM -0400, J. Bruce Fields wrote:
> From: "J. Bruce Fields" <bfields@redhat.com>
> 
> Each rpc_client has a cl_clid which is allocated from a global ida, and
> a debugfs directory which is named after cl_clid.
> 
> We're releasing the cl_clid before we free the debugfs directory named
> after it.  As soon as the cl_clid is released, that value is available
> for another newly created client.
> 
> That leaves a window where another client may attempt to create a new
> debugfs directory with the same name as the not-yet-deleted debugfs
> directory from the dying client.  Symptoms are log messages like
> 
> 	Directory 4 with parent 'rpc_clnt' already present!

This also cleared up a "file-max limit 199277 reached" warning, which
suggests to me a leak in an error path somewhere (I think everything's
supposed to work normally even if debugfs file createion fails), but I
don't see it.

--b.

> 
> Fixes: 7c4310ff5642 "SUNRPC: defer slow parts of rpc_free_client() to a workqueue."
> Signed-off-by: J. Bruce Fields <bfields@redhat.com>
> ---
>  net/sunrpc/clnt.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/net/sunrpc/clnt.c b/net/sunrpc/clnt.c
> index 8350d3a2e9a7..4a7efc00fd83 100644
> --- a/net/sunrpc/clnt.c
> +++ b/net/sunrpc/clnt.c
> @@ -889,6 +889,7 @@ static void rpc_free_client_work(struct work_struct *work)
>  	 * here.
>  	 */
>  	rpc_clnt_debugfs_unregister(clnt);
> +	rpc_free_clid(clnt);
>  	rpc_clnt_remove_pipedir(clnt);
>  
>  	kfree(clnt);
> @@ -910,7 +911,6 @@ rpc_free_client(struct rpc_clnt *clnt)
>  	xprt_put(rcu_dereference_raw(clnt->cl_xprt));
>  	xprt_iter_destroy(&clnt->cl_xpi);
>  	put_cred(clnt->cl_cred);
> -	rpc_free_clid(clnt);
>  
>  	INIT_WORK(&clnt->cl_work, rpc_free_client_work);
>  	schedule_work(&clnt->cl_work);
> -- 
> 2.26.2

  reply	other threads:[~2020-05-13 22:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-13 22:38 [PATCH] SUNRPC: 'Directory with parent 'rpc_clnt' already present!' J. Bruce Fields
2020-05-13 22:40 ` J. Bruce Fields [this message]
2020-05-13 23:29   ` J. Bruce Fields

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=20200513224033.GA1415@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=bfields@redhat.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=schumakeranna@gmail.com \
    --cc=trondmy@hammerspace.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