From: Jeff Layton <jlayton@kernel.org>
To: Prabhakar Pujeri <prabhakar.pujeri@dell.com>, steved@redhat.com
Cc: cel@kernel.org, linux-nfs@vger.kernel.org
Subject: Re: [PATCH v1 0/3] nfsdctl: list NFSv4 clients
Date: Fri, 28 Aug 2026 10:37:10 -0400 [thread overview]
Message-ID: <b5e772f9d0e0aaae7e36320032518ce57139170d.camel@kernel.org> (raw)
In-Reply-To: <cover.1787639206.git.prabhakar.pujeri@dell.com>
On Tue, 2026-08-25 at 06:52 +0000, Prabhakar Pujeri wrote:
> Add the userspace consumer for the companion NFSD Netlink client-state
> series, whose cover Message-ID is:
>
> <cover.1787638668.git.prabhakar.pujeri@dell.com>
>
> The series mirrors the kernel ABI split:
>
> 1. Display the explicit recovery-grace value returned by threads-get.
> 2. Add a privileged `nfsdctl clients` table for basic client state.
> 3. Extend the table with session and stateid record counts.
>
> Attribute presence remains the compatibility boundary. An older kernel
> omits the grace value, and missing count attributes are displayed as
> dashes. The bundled UAPI header permits building before the new kernel
> header is installed. The configure probe requires the final count
> attribute, so a system header containing only the base client command also
> falls back to the complete bundled copy.
>
> Validation performed:
>
> - full nfs-utils build at each applicable patch state
> - final `make check`: no failures; one environment-dependent test skipped
> - bundled nfsd Netlink UAPI compared byte-for-byte with the kernel copy
> - two-vCPU QEMU test with a live NFSv4.2 loopback mount
> - grace yes/no transitions displayed by `nfsdctl threads`
> - live client row showing one session, open stateid, lock stateid, and
> delegation stateid; zero layout stateids
> - callback, reclaim, lease, peer-address, and client-ID fields checked
>
> The series is based on the current nfs-utils master branch. The exact base
> is recorded in the base-commit trailer below.
>
> Prabhakar Pujeri (3):
> nfsdctl: report NFSv4 grace state
> nfsdctl: add a command to list NFSv4 clients
> nfsdctl: display per-client NFSv4 state usage
>
> configure.ac | 2 +-
> support/include/nfsd_netlink.h | 41 +++++
> utils/nfsdctl/nfsdctl.8 | 22 ++-
> utils/nfsdctl/nfsdctl.adoc | 15 +-
> utils/nfsdctl/nfsdctl.c | 268 +++++++++++++++++++++++++++++++++
> 5 files changed, 345 insertions(+), 3 deletions(-)
>
>
> base-commit: 67ed1bdb1af1c70a5fd3b377a997401b7676b827
Sashiko has some comments about this that probably need to be addressed
before we apply these. There is potential for a softlockup in patch #3,
in particular:
https://sashiko.dev/#/patchset/cover.1787638668.git.prabhakar.pujeri%40dell.com
--
Jeff Layton <jlayton@kernel.org>
next prev parent reply other threads:[~2026-08-28 14:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-25 6:52 [PATCH v1 0/3] nfsdctl: list NFSv4 clients Prabhakar Pujeri
2026-08-25 6:52 ` [PATCH v1 1/3] nfsdctl: report NFSv4 grace state Prabhakar Pujeri
2026-08-25 6:52 ` [PATCH v1 2/3] nfsdctl: add a command to list NFSv4 clients Prabhakar Pujeri
2026-08-25 6:52 ` [PATCH v1 3/3] nfsdctl: display per-client NFSv4 state usage Prabhakar Pujeri
2026-08-28 14:37 ` Jeff Layton [this message]
2026-08-29 21:28 ` [PATCH v1 0/3] nfsdctl: list NFSv4 clients Steve Dickson
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=b5e772f9d0e0aaae7e36320032518ce57139170d.camel@kernel.org \
--to=jlayton@kernel.org \
--cc=cel@kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=prabhakar.pujeri@dell.com \
--cc=steved@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox