From: "J. Bruce Fields" <bfields@redhat.com>
To: "J. Bruce Fields" <bfields@fieldses.org>
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 19:29:37 -0400 [thread overview]
Message-ID: <20200513232937.GB34451@pick.fieldses.org> (raw)
In-Reply-To: <20200513224033.GA1415@fieldses.org>
On Wed, May 13, 2020 at 06:40:33PM -0400, J. Bruce Fields wrote:
> 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.
Whoops, I spoke to soon, I'm still seeing that warning, so that's an
unrelated issue.
--b.
prev parent reply other threads:[~2020-05-13 23:29 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
2020-05-13 23:29 ` J. Bruce Fields [this message]
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=20200513232937.GB34451@pick.fieldses.org \
--to=bfields@redhat.com \
--cc=bfields@fieldses.org \
--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