Netdev List
 help / color / mirror / Atom feed
From: "Chuck Lever" <cel@kernel.org>
To: "Jeff Layton" <jlayton@kernel.org>, NeilBrown <neil@brown.name>,
	"Olga Kornievskaia" <okorniev@redhat.com>,
	"Dai Ngo" <Dai.Ngo@oracle.com>, "Tom Talpey" <tom@talpey.com>,
	"Trond Myklebust" <trondmy@kernel.org>,
	"Anna Schumaker" <anna@kernel.org>,
	"David S. Miller" <davem@davemloft.net>,
	"Eric Dumazet" <edumazet@google.com>,
	"Jakub Kicinski" <kuba@kernel.org>,
	"Paolo Abeni" <pabeni@redhat.com>,
	"Simon Horman" <horms@kernel.org>,
	"J. Bruce Fields" <bfields@fieldses.org>,
	"Shuah Khan" <shuah@kernel.org>
Cc: linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org,
	netdev@vger.kernel.org, "Trond Myklebust" <trondmy@gmail.com>,
	linux-kselftest@vger.kernel.org
Subject: Re: [PATCH v2 8/8] selftests/nfsd: add a per-netns rpcbind stub and the listener round-trips
Date: Tue, 11 Aug 2026 15:14:33 -0400	[thread overview]
Message-ID: <59d69859-6a41-40e6-957c-23159313956f@app.fastmail.com> (raw)
In-Reply-To: <20260811-nfsd-nl-hang-v2-8-c0c92b3953c3@kernel.org>



On Tue, Aug 11, 2026, at 8:03 AM, Jeff Layton wrote:
> Creating a listener registers with rpcbind: svc_xprt_create_from_sa() passes
> flags of 0, so pmap_register is true in svc_setup_socket(), and
> nfsd_version3 is enabled by default and does not set vs_rpcb_optnl, so a
> registration failure aborts listener creation. A fresh netns has no rpcbind,
> and reaching the host's is not an option -- svc_rpcb_setup() opens by
> calling svc_unregister(), which would clear the host's nfsd entries.

>  /* --------------------------- fixture --------------------------- */
> 
>  FIXTURE(nfsd_listener) {
> -	int placeholder;
> +	pid_t rpcbd;
>  };
> 
>  FIXTURE_SETUP(nfsd_listener)
> @@ -369,14 +665,35 @@ FIXTURE_SETUP(nfsd_listener)
>  	nfsd_family = genl_resolve_nfsd();
>  	if (nfsd_family < 0)
>  		SKIP(return, "nfsd genl family not found (modprobe nfsd?)");
> +
> +	if (rpcb_stats_alloc() < 0)
> +		SKIP(return, "mmap(rpcbind stub counters): %s", strerror(errno));
> +
> +	self->rpcbd = rpcb_stub_start(RPCB_STUB_ACCEPT);
> +	if (self->rpcbd < 0)
> +		SKIP(return, "cannot start the rpcbind stub: %s",
> +		     strerror(errno));
>  }
> 
>  FIXTURE_TEARDOWN(nfsd_listener)
>  {
> +	if (self->rpcbd > 0) {
> +		kill(self->rpcbd, SIGKILL);
> +		waitpid(self->rpcbd, NULL, 0);
> +	}
> +	if (rpcb_stats) {
> +		munmap((void *)rpcb_stats, sizeof(*rpcb_stats));
> +		rpcb_stats = NULL;
> +	}
>  }

The fixture appears to leak the network namespace for the tests that
finish with a listener still up. Would something along these lines in
FIXTURE_TEARDOWN() cover it?

	/* A live listener pins the netns; drop any serv the test made. */
	if (listener_set(NULL, 0) == -EBUSY)
		threads_set(0);


-- 
Chuck Lever

      reply	other threads:[~2026-08-11 19:14 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-11 12:02 [PATCH v2 0/8] nfsd/sunrpc: harden the netlink listener interfaces Jeff Layton
2026-08-11 12:03 ` [PATCH v2 1/8] NFSD: validate transport name in listener_set before serv creation Jeff Layton
2026-08-11 12:03 ` [PATCH v2 2/8] NFSD: cap the number of listeners accepted in listener_set Jeff Layton
2026-08-11 12:03 ` [PATCH v2 3/8] SUNRPC: keep the first error in svc_register() Jeff Layton
2026-08-11 12:03 ` [PATCH v2 4/8] SUNRPC: undo partial rpcbind registrations when svc_register() fails Jeff Layton
2026-08-11 19:19   ` Chuck Lever
2026-08-12 19:38     ` Jeff Layton
2026-08-12 19:57       ` Chuck Lever
2026-08-14 11:01         ` Jeff Layton
2026-08-14 15:28           ` Chuck Lever
2026-08-11 12:03 ` [PATCH v2 5/8] SUNRPC: bound the local rpcbind client timeout to 1s Jeff Layton
2026-08-11 12:03 ` [PATCH v2 6/8] NFSD: report listener creation failures through extack Jeff Layton
2026-08-11 12:03 ` [PATCH v2 7/8] selftests/nfsd: exercise listener_set request validation Jeff Layton
2026-08-11 12:03 ` [PATCH v2 8/8] selftests/nfsd: add a per-netns rpcbind stub and the listener round-trips Jeff Layton
2026-08-11 19:14   ` Chuck Lever [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=59d69859-6a41-40e6-957c-23159313956f@app.fastmail.com \
    --to=cel@kernel.org \
    --cc=Dai.Ngo@oracle.com \
    --cc=anna@kernel.org \
    --cc=bfields@fieldses.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=jlayton@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=neil@brown.name \
    --cc=netdev@vger.kernel.org \
    --cc=okorniev@redhat.com \
    --cc=pabeni@redhat.com \
    --cc=shuah@kernel.org \
    --cc=tom@talpey.com \
    --cc=trondmy@gmail.com \
    --cc=trondmy@kernel.org \
    /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