From: schumaker.anna@gmail.com
To: Trond.Myklebust@hammerspace.com, linux-nfs@vger.kernel.org
Cc: Anna.Schumaker@Netapp.com
Subject: [PATCH 0/5] NFS: Re-probe server capabilities on remount
Date: Thu, 14 Oct 2021 13:55:03 -0400 [thread overview]
Message-ID: <20211014175508.197313-1-Anna.Schumaker@Netapp.com> (raw)
From: Anna Schumaker <Anna.Schumaker@Netapp.com>
These patches hook into the nfs_reconfigure() function to reset and
reprobe a server's capabilities when remounted. This could be useful if
a server is upgraded to support a new NFS v4.2 feature or if it has
other changes that can only be detected at mount-time.
Thoughts?
Anna
Anna Schumaker (5):
NFS: Create an nfs4_server_set_init_caps() function
NFS: Move nfs_probe_destination() into the generic client
NFS: Replace calls to nfs_probe_fsinfo() with nfs_probe_server()
NFS: Call nfs_probe_server() during a fscontext-reconfigure event
NFS: Unexport nfs_probe_fsinfo()
fs/nfs/client.c | 37 ++++++++++++++++++--------
fs/nfs/internal.h | 3 ++-
fs/nfs/nfs4client.c | 65 ++++++++++++++-------------------------------
fs/nfs/nfs4proc.c | 2 ++
fs/nfs/super.c | 7 ++++-
5 files changed, 56 insertions(+), 58 deletions(-)
--
2.33.0
next reply other threads:[~2021-10-14 17:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-14 17:55 schumaker.anna [this message]
2021-10-14 17:55 ` [PATCH 1/5] NFS: Create an nfs4_server_set_init_caps() function schumaker.anna
2021-10-14 17:55 ` [PATCH 2/5] NFS: Move nfs_probe_destination() into the generic client schumaker.anna
2021-10-14 17:55 ` [PATCH 3/5] NFS: Replace calls to nfs_probe_fsinfo() with nfs_probe_server() schumaker.anna
2021-10-14 17:55 ` [PATCH 4/5] NFS: Call nfs_probe_server() during a fscontext-reconfigure event schumaker.anna
2021-10-14 17:55 ` [PATCH 5/5] NFS: Unexport nfs_probe_fsinfo() schumaker.anna
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=20211014175508.197313-1-Anna.Schumaker@Netapp.com \
--to=schumaker.anna@gmail.com \
--cc=Anna.Schumaker@Netapp.com \
--cc=Trond.Myklebust@hammerspace.com \
--cc=linux-nfs@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.