Received-SPF: pass (google.com: domain of linux-nfs-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
From:   Benjamin Coddington <bcodding@redhat.com>
To:     linux-nfs@vger.kernel.org
Subject: [PATCH 0/9 RFC v2] NFS sysfs scaffolding
Date:   Fri, 21 Apr 2023 13:08:03 -0400
Message-Id: <cover.1682096307.git.bcodding@redhat.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Precedence: bulk

Here's another round of sysfs entries for each nfs_server, this time with a
single use-case: a "shutdown" toggle that causes the basic rpc_clnt(s) to
immediately fail tasks with -EIO.  It works well for the non pNFS cases to
allow an unmount of a filesystem when the NFS server has gone away.

I'm posting to gain potential NACKing, or to be redirected, or to serve as
fodder for discussion at LSF.

I'm thinking I'd like to toggle v4.2 things like READ_PLUS in here next, or
other module-level options that maybe would be useful per-mount.

Benjamin Coddington (9):
  NFS: rename nfs_client_kset to nfs_kset
  NFS: rename nfs_client_kobj to nfs_net_kobj
  NFS: add superblock sysfs entries
  NFS: Add sysfs links to sunrpc clients for nfs_clients
  NFS: add a sysfs link to the lockd rpc_client
  NFS: add a sysfs link to the acl rpc_client
  NFS: add sysfs shutdown knob
  NFS: Cleanup unused rpc_clnt variable
  NFSv4: Clean up some shutdown loops

 fs/lockd/clntlock.c         |   6 ++
 fs/nfs/client.c             |  21 +++++
 fs/nfs/nfs3client.c         |   4 +
 fs/nfs/nfs4client.c         |   2 +
 fs/nfs/nfs4proc.c           |   2 +-
 fs/nfs/nfs4state.c          |   5 +-
 fs/nfs/super.c              |   6 +-
 fs/nfs/sysfs.c              | 148 +++++++++++++++++++++++++++++++++---
 fs/nfs/sysfs.h              |   9 ++-
 include/linux/lockd/bind.h  |   2 +
 include/linux/nfs_fs_sb.h   |   3 +
 include/linux/sunrpc/clnt.h |  11 ++-
 net/sunrpc/clnt.c           |   5 ++
 net/sunrpc/sysfs.h          |   7 --
 14 files changed, 204 insertions(+), 27 deletions(-)

-- 
2.39.2