From: Chuck Lever <chuck.lever@oracle.com>
To: Olga Kornievskaia <okorniev@redhat.com>, jlayton@kernel.org
Cc: linux-nfs@vger.kernel.org, neilb@brown.name, Dai.Ngo@oracle.com,
tom@talpey.com
Subject: Re: [PATCH 1/1] NFSD: don't start nfsd if sv_permsocks is empty
Date: Fri, 31 Oct 2025 08:51:44 -0400 [thread overview]
Message-ID: <bca68f1b-ca56-4e94-abd0-de4c509d3d00@oracle.com> (raw)
In-Reply-To: <20251030163532.54626-1-okorniev@redhat.com>
On 10/30/25 12:35 PM, Olga Kornievskaia wrote:
> Previously, while trying to create a server instance, if no
> listening sockets were present then default parameter udp
> and tcp listeners were created. It's unclear what purpose
> was of starting these listeners were and how this could have
> been triggered by the userland setup. This patch proposed
> to ensure the reverse that we never end in a situation where
> no listener sockets are created and we are trying to create
> nfsd threads.
>
> The problem it solves is: when nfs.conf only has tcp=n (and
> nothing else for the choice of transports), nfsdctl would
> still start the server and create udp and tcp listeners.
>
Fixes: ?
One more below.
> Signed-off-by: Olga Kornievskaia <okorniev@redhat.com>
> ---
> fs/nfsd/nfssvc.c | 28 +++++-----------------------
> 1 file changed, 5 insertions(+), 23 deletions(-)
>
> diff --git a/fs/nfsd/nfssvc.c b/fs/nfsd/nfssvc.c
> index 7057ddd7a0a8..40592b61b04b 100644
> --- a/fs/nfsd/nfssvc.c
> +++ b/fs/nfsd/nfssvc.c
> @@ -249,27 +249,6 @@ int nfsd_nrthreads(struct net *net)
> return rv;
> }
>
> -static int nfsd_init_socks(struct net *net, const struct cred *cred)
> -{
> - int error;
> - struct nfsd_net *nn = net_generic(net, nfsd_net_id);
> -
> - if (!list_empty(&nn->nfsd_serv->sv_permsocks))
> - return 0;
> -
> - error = svc_xprt_create(nn->nfsd_serv, "udp", net, PF_INET, NFS_PORT,
> - SVC_SOCK_DEFAULTS, cred);
> - if (error < 0)
> - return error;
> -
> - error = svc_xprt_create(nn->nfsd_serv, "tcp", net, PF_INET, NFS_PORT,
> - SVC_SOCK_DEFAULTS, cred);
> - if (error < 0)
> - return error;
> -
> - return 0;
> -}
> -
> static int nfsd_users = 0;
>
> static int nfsd_startup_generic(void)
> @@ -377,9 +356,12 @@ static int nfsd_startup_net(struct net *net, const struct cred *cred)
> ret = nfsd_startup_generic();
> if (ret)
> return ret;
> - ret = nfsd_init_socks(net, cred);
> - if (ret)
> +
> + if (list_empty(&nn->nfsd_serv->sv_permsocks)) {
> + pr_warn("NFSD: not starting because no listening sockets found\n");
I know the code refers to sockets, but the term doesn't refer to RDMA
listeners at all, and this warning seems applicable to both socket-based
and RDMA transports. How about:
NFSD: No available listeners
> + ret = -EIO;
> goto out_socks;
> + }
>
> if (nfsd_needs_lockd(nn) && !nn->lockd_up) {
> ret = lockd_up(net, cred);
--
Chuck Lever
next prev parent reply other threads:[~2025-10-31 12:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-30 16:35 [PATCH 1/1] NFSD: don't start nfsd if sv_permsocks is empty Olga Kornievskaia
2025-10-30 17:53 ` Jeff Layton
2025-10-30 23:05 ` NeilBrown
2025-10-31 17:26 ` Olga Kornievskaia
2025-10-31 12:51 ` Chuck Lever [this message]
2025-10-31 17:26 ` Olga Kornievskaia
2025-10-31 23:41 ` NeilBrown
2025-11-02 15:46 ` Chuck Lever
2025-11-02 22:11 ` NeilBrown
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=bca68f1b-ca56-4e94-abd0-de4c509d3d00@oracle.com \
--to=chuck.lever@oracle.com \
--cc=Dai.Ngo@oracle.com \
--cc=jlayton@kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=neilb@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;
as well as URLs for NNTP newsgroup(s).