From: Chuck Lever <cel@kernel.org>
To: NeilBrown <neilb@ownmail.net>, Jeff Layton <jlayton@kernel.org>,
Olga Kornievskaia <okorniev@redhat.com>,
Dai Ngo <dai.ngo@oracle.com>, Tom Talpey <tom@talpey.com>
Cc: <linux-nfs@vger.kernel.org>, Chuck Lever <chuck.lever@oracle.com>
Subject: [PATCH v7 0/2] NFSD: move accumulated callback ops to per-net namespace
Date: Fri, 13 Mar 2026 12:31:46 -0400 [thread overview]
Message-ID: <20260313163148.281676-1-cel@kernel.org> (raw)
From: Chuck Lever <chuck.lever@oracle.com>
In preparation to merge Dai's patch, I've updated it to address
several outstanding review comments.
Base commit: 01b8a53aac4e46f04bcde3049d300ed81479aeb7
---
v2:
. free memory allocated for nn->nfsd_cb_version4.counts in
nfsd_net_cb_stats_init() on error in nfsd_net_init().
v3:
. reword commit message.
. fix initialization of nn->nfsd_cb_program.nrvers.
v4:
. fix merge conflict in nfsd_net_exit in nfsd-testing branch.
v5:
. restore commit message to the original in v1
v6:
. put the call nfsd_net_cb_stats_init and nfsd_net_cb_stats_shutdown
under CONFIG_NFSD_V4.
. reword commit message to clarify the intention of the patch.
v7:
. Use proper symbolic constants instead of raw integers
. Split the .p_statidx change into a pre-requisite patch
. Add kernel-doc comments to new non-static functions
Chuck Lever (1):
NFSD: use per-operation statidx for callback procedures
Dai Ngo (1):
NFSD: convert callback RPC program to per-net namespace
fs/nfsd/netns.h | 3 ++
fs/nfsd/nfs4callback.c | 113 ++++++++++++++++++++++++++++-------------
fs/nfsd/nfsctl.c | 5 ++
fs/nfsd/state.h | 9 ++++
4 files changed, 95 insertions(+), 35 deletions(-)
--
2.53.0
next reply other threads:[~2026-03-13 16:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-13 16:31 Chuck Lever [this message]
2026-03-13 16:31 ` [PATCH v7 1/2] NFSD: use per-operation statidx for callback procedures Chuck Lever
2026-03-14 11:55 ` Jeff Layton
2026-03-13 16:31 ` [PATCH v7 2/2] NFSD: convert callback RPC program to per-net namespace Chuck Lever
2026-03-14 12:04 ` Jeff Layton
2026-03-14 15:47 ` Chuck Lever
2026-03-14 23:01 ` 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=20260313163148.281676-1-cel@kernel.org \
--to=cel@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=dai.ngo@oracle.com \
--cc=jlayton@kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=neilb@ownmail.net \
--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