From: Jeff Layton <jlayton@kernel.org>
To: Chuck Lever <cel@kernel.org>
Cc: NeilBrown <neil@brown.name>,
Olga Kornievskaia <okorniev@redhat.com>,
Dai Ngo <Dai.Ngo@oracle.com>, Tom Talpey <tom@talpey.com>,
Shuah Khan <shuah@kernel.org>,
linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org
Subject: Re: [PATCH 8/8] selftests/nfsd: add a cross-namespace control-plane soak
Date: Mon, 21 Sep 2026 15:09:33 -0400 [thread overview]
Message-ID: <0c9a044319a2e74770df0625a50a62933cb69d4e.camel@kernel.org> (raw)
In-Reply-To: <bc472084-1e3e-40bb-aade-6fd7aefaed4b@slotpi15m67>
On Mon, 2026-09-21 at 14:20 -0400, Chuck Lever wrote:
> On Mon, Sep 21, 2026, Jeff Layton wrote:
> > ---
> > tools/testing/selftests/nfsd/Makefile | 1 +
> > tools/testing/selftests/nfsd/config | 6 +
> > tools/testing/selftests/nfsd/nfsd_netns_isolation | Bin 0 -> 49192 bytes
> > tools/testing/selftests/nfsd/nfsd_netns_stress | Bin 0 -> 39232 bytes
> > tools/testing/selftests/nfsd/nfsd_netns_stress.c | 572 ++++++++++++++++++++++
> > tools/testing/selftests/nfsd/settings | 2 +-
> > 6 files changed, 580 insertions(+), 1 deletion(-)
>
> Hi Jeff,
>
> Did you intend to commit the nfsd_netns_isolation and nfsd_netns_stress
> binaries?
>
>
Nope. Sashiko pointed that out too. I'm fixing it now (along with
another issue) and will send a v2.
Thanks!
> > diff --git a/tools/testing/selftests/nfsd/Makefile b/tools/testing/selftests/nfsd/Makefile
> > index 2b7c44c3fb00..b29bf642c0ad 100644
> > --- a/tools/testing/selftests/nfsd/Makefile
> > +++ b/tools/testing/selftests/nfsd/Makefile
> > @@ -3,5 +3,6 @@ CFLAGS += $(KHDR_INCLUDES) -Wall
> >
> > TEST_GEN_PROGS := nfsd_netlink_listener
> > TEST_GEN_PROGS += nfsd_netns_isolation
> > +TEST_GEN_PROGS += nfsd_netns_stress
> >
> > include ../lib.mk
--
Jeff Layton <jlayton@kernel.org>
next prev parent reply other threads:[~2026-09-21 19:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-21 16:31 [PATCH 0/8] nfsd: reduce the scope of the nfsd_mutex Jeff Layton
2026-09-21 16:31 ` [PATCH 1/8] nfsd: clear NFSD_NET_UP before dropping the generic resource reference Jeff Layton
2026-09-21 16:31 ` [PATCH 2/8] nfsd: make max_blksize a per-namespace setting Jeff Layton
2026-09-21 16:31 ` [PATCH 3/8] nfsd: move the control plane to a per-namespace mutex Jeff Layton
2026-09-21 16:31 ` [PATCH 4/8] nfsd: rename nfsd_mutex to nfsd_global_mutex Jeff Layton
2026-09-21 16:31 ` [PATCH 5/8] nfsd: give the open file cache its own mutex Jeff Layton
2026-09-22 6:37 ` NeilBrown
2026-09-22 10:18 ` Jeff Layton
2026-09-21 16:31 ` [PATCH 6/8] selftests/nfsd: factor the netlink plumbing into a shared header Jeff Layton
2026-09-21 16:31 ` [PATCH 7/8] selftests/nfsd: add cross-namespace isolation tests Jeff Layton
2026-09-21 16:31 ` [PATCH 8/8] selftests/nfsd: add a cross-namespace control-plane soak Jeff Layton
2026-09-21 18:20 ` Chuck Lever
2026-09-21 19:09 ` Jeff Layton [this message]
2026-09-22 6:39 ` [PATCH 0/8] nfsd: reduce the scope of the nfsd_mutex 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=0c9a044319a2e74770df0625a50a62933cb69d4e.camel@kernel.org \
--to=jlayton@kernel.org \
--cc=Dai.Ngo@oracle.com \
--cc=cel@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=okorniev@redhat.com \
--cc=shuah@kernel.org \
--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
all inboxes | Powered by JetHome®