From: Jeff Layton <jlayton@kernel.org>
To: Chuck Lever <chuck.lever@oracle.com>,
Olga Kornievskaia <okorniev@redhat.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: [PATCH 3/3] nfsd: fix management of listener transports
Date: Thu, 16 Jan 2025 09:46:11 -0500 [thread overview]
Message-ID: <62694be2aea08c40af7b0cea9d8c1b67a7b2cbe7.camel@kernel.org> (raw)
In-Reply-To: <62d3ced2-8c90-4699-b3c4-c58489ec9f19@oracle.com>
On Thu, 2025-01-16 at 09:27 -0500, Chuck Lever wrote:
> On 1/15/25 6:24 PM, Olga Kornievskaia wrote:
> > When a particular listener is being removed we need to make sure
> > that we delete the entry from the list of permanent sockets
> > (sv_permsocks) as well as remove it from the listener transports
> > (sp_xprts). When adding back the leftover transports not being
> > removed we need to clear XPT_BUSY flag so that it can be used.
> >
> > Fixes: 16a471177496 ("NFSD: add listener-{set,get} netlink command")
> > Signed-off-by: Olga Kornievskaia <okorniev@redhat.com>
> > ---
> > fs/nfsd/nfsctl.c | 4 +++-
> > 1 file changed, 3 insertions(+), 1 deletion(-)
> >
> > diff --git a/fs/nfsd/nfsctl.c b/fs/nfsd/nfsctl.c
> > index 95ea4393305b..3deedd511e83 100644
> > --- a/fs/nfsd/nfsctl.c
> > +++ b/fs/nfsd/nfsctl.c
> > @@ -1988,7 +1988,7 @@ int nfsd_nl_listener_set_doit(struct sk_buff *skb, struct genl_info *info)
> > /* Close the remaining sockets on the permsocks list */
> > while (!list_empty(&permsocks)) {
> > xprt = list_first_entry(&permsocks, struct svc_xprt, xpt_list);
> > - list_move(&xprt->xpt_list, &serv->sv_permsocks);
> > + list_del_init(&xprt->xpt_list);
> >
> > /*
> > * Newly-created sockets are born with the BUSY bit set. Clear
> > @@ -2000,6 +2000,7 @@ int nfsd_nl_listener_set_doit(struct sk_buff *skb, struct genl_info *info)
> >
> > set_bit(XPT_CLOSE, &xprt->xpt_flags);
> > spin_unlock_bh(&serv->sv_lock);
> > + svc_xprt_dequeue_entry(xprt);
>
> The kdoc comment in front of llist_del_entry() says:
>
> + * The caller must ensure that nothing can race in and change the
> + * list while this is running.
>
> In this caller, I don't see how such a race is prevented.
>
This caller holds the nfsd_mutex, and prior to this, it does:
/* For now, no removing old sockets while server is running */
if (serv->sv_nrthreads && !list_empty(&permsocks)) {
list_splice_init(&permsocks, &serv->sv_permsocks);
spin_unlock_bh(&serv->sv_lock);
err = -EBUSY;
goto out_unlock_mtx;
}
No nfsd threads are running and none can be started, so nothing is
processing the queue at this time. Some comments explaining that would
be a welcome addition here.
>
> > svc_xprt_close(xprt);
> > spin_lock_bh(&serv->sv_lock);
> > }
> > @@ -2031,6 +2032,7 @@ int nfsd_nl_listener_set_doit(struct sk_buff *skb, struct genl_info *info)
> >
> > xprt = svc_find_listener(serv, xcl_name, net, sa);
> > if (xprt) {
> > + clear_bit(XPT_BUSY, &xprt->xpt_flags);
> > svc_xprt_put(xprt);
> > continue;
> > }
>
>
--
Jeff Layton <jlayton@kernel.org>
next prev parent reply other threads:[~2025-01-16 14:46 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-15 23:24 [PATCH 0/3] fix removal of nfsd listeners Olga Kornievskaia
2025-01-15 23:24 ` [PATCH 1/3] llist: add ability to remove a particular entry from the list Olga Kornievskaia
2025-01-16 14:26 ` Chuck Lever
2025-01-16 14:54 ` Olga Kornievskaia
2025-01-16 15:33 ` Chuck Lever
2025-01-16 15:42 ` Jeff Layton
2025-01-16 16:00 ` Chuck Lever
2025-01-16 16:31 ` Olga Kornievskaia
2025-01-16 16:44 ` Chuck Lever
2025-01-17 4:08 ` kernel test robot
2025-01-17 4:08 ` kernel test robot
2025-01-24 0:57 ` kernel test robot
2025-01-15 23:24 ` [PATCH 2/3] SUNRPC: add ability to remove specific server transport Olga Kornievskaia
2025-01-15 23:24 ` [PATCH 3/3] nfsd: fix management of listener transports Olga Kornievskaia
2025-01-16 14:27 ` Chuck Lever
2025-01-16 14:46 ` Jeff Layton [this message]
2025-01-16 14:55 ` Chuck Lever
2025-01-16 15:34 ` Olga Kornievskaia
2025-01-16 15:42 ` Chuck Lever
2025-01-16 11:53 ` [PATCH 0/3] fix removal of nfsd listeners Jeff Layton
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=62694be2aea08c40af7b0cea9d8c1b67a7b2cbe7.camel@kernel.org \
--to=jlayton@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=linux-nfs@vger.kernel.org \
--cc=okorniev@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.