From: bfields@fieldses.org (J. Bruce Fields)
To: Steve Dickson <steved@redhat.com>
Cc: Linux NFS Mailing list <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH RFC 0/3] Remove NFS v2 support from the client and server
Date: Mon, 29 Nov 2021 17:40:00 -0500 [thread overview]
Message-ID: <20211129224000.GF24258@fieldses.org> (raw)
In-Reply-To: <20211129192731.783466-1-steved@redhat.com>
On Mon, Nov 29, 2021 at 02:27:28PM -0500, Steve Dickson wrote:
> These patches will remove the all references and
> support of NFS v2 in both the server and client.
>
> On server side the support has been off, by default,
> since 2013 (6b4e4965a6b). With this server patch the
> ability to enable v2 will be remove.
>
> Currently even with CONFIG_NFS_V2 not set
> v2 mounts are still tied (over-the-wire).
So the client is running a kernel built with CONFIG_NFS_V2 not set, and
you're still seeing it send NFSv2 calls?
That's very weird.
> I looked at creating a kernel parameter module so support could
> re-enabled but that got ugly quick.
I don't think there's much point to a module parameter.
One other thing we might want to do is provide a way for distros to
configure out support on the server side too. That'd help confirm that
people really aren't using it before we tear it out completely.
E.g., untested, and should probably remove more than this, but as a
start:
diff --git a/fs/nfsd/Kconfig b/fs/nfsd/Kconfig
index 3d1d17256a91..7b9e9afc5fcb 100644
--- a/fs/nfsd/Kconfig
+++ b/fs/nfsd/Kconfig
@@ -35,6 +35,16 @@ config NFSD_V2_ACL
bool
depends on NFSD
+config NFSD_V2
+ bool "NFS server support for NFS version 2"
+ depends on NFSD
+ help
+ This option enables server support for version 2 of the NFS
+ protocol. This version has significant limitations and is no
+ longer widely used.
+
+ If unsure, say N.
+
config NFSD_V3
bool "NFS server support for NFS version 3"
depends on NFSD
diff --git a/fs/nfsd/nfssvc.c b/fs/nfsd/nfssvc.c
index 80431921e5d7..09c376063ff0 100644
--- a/fs/nfsd/nfssvc.c
+++ b/fs/nfsd/nfssvc.c
@@ -116,7 +116,9 @@ static struct svc_stat nfsd_acl_svcstats = {
#endif /* defined(CONFIG_NFSD_V2_ACL) || defined(CONFIG_NFSD_V3_ACL) */
static const struct svc_version *nfsd_version[] = {
+#if defined(CONFIG_NFSD_V2)
[2] = &nfsd_version2,
+#endif
#if defined(CONFIG_NFSD_V3)
[3] = &nfsd_version3,
#endif
prev parent reply other threads:[~2021-11-29 23:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-29 19:27 [PATCH RFC 0/3] Remove NFS v2 support from the client and server Steve Dickson
2021-11-29 19:27 ` [PATCH RFC 1/3] nfsd: Remove the ability to enable NFS v2 Steve Dickson
2021-11-29 19:27 ` [PATCH RFC 2/3] nfs.man: Remove references to NFS v2 from the man pages Steve Dickson
2021-11-29 19:27 ` [PATCH RFC 3/3] mount: Remove NFS v2 support from mount.nfs Steve Dickson
2021-11-29 20:38 ` [PATCH RFC 0/3] Remove NFS v2 support from the client and server NeilBrown
2021-11-29 21:13 ` Steve Dickson
2021-11-29 22:40 ` J. Bruce Fields [this message]
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=20211129224000.GF24258@fieldses.org \
--to=bfields@fieldses.org \
--cc=linux-nfs@vger.kernel.org \
--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