From: Jeff Layton <jlayton@kernel.org>
To: Steve Dickson <steved@redhat.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: [PATCH 0/2] nfsd/nfsdctl: default to starting with v4.0 servers disabled
Date: Fri, 09 Jan 2026 14:04:32 -0500 [thread overview]
Message-ID: <d71e37c054c51428f34a51b6a980a62bc07a68e7.camel@kernel.org> (raw)
In-Reply-To: <20251008-master-v1-0-c879be4973c8@kernel.org>
On Wed, 2025-10-08 at 16:13 -0400, Jeff Layton wrote:
> At this week's NFS Bakeathon, we had a discussion around deprecating the
> NFSv4.0 protocol. To prepare for that eventuality, make the NFS server
> only accept NFSv4.0 if it was explicitly requested in the config file or
> in command-line options.
>
> Signed-off-by: Jeff Layton <jlayton@kernel.org>
> ---
> Jeff Layton (2):
> nfsd: disable v4.0 by default
> nfsdctl: disable v4.0 by default
>
> utils/nfsd/nfsd.c | 5 +++--
> utils/nfsdctl/nfsdctl.c | 2 +-
> 2 files changed, 4 insertions(+), 3 deletions(-)
> ---
> base-commit: 612e407c46b848932c32be00b835a7b5317e3d08
> change-id: 20251008-master-724587cca99a
>
> Best regards,
Steved, ping?
Also, if anyone else wants to send an Acked-by for this, I wouldn't
complain.
Cheers,
--
Jeff Layton <jlayton@kernel.org>
next prev parent reply other threads:[~2026-01-09 19:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-08 20:13 [PATCH 0/2] nfsd/nfsdctl: default to starting with v4.0 servers disabled Jeff Layton
2025-10-08 20:13 ` [PATCH 1/2] nfsd: disable v4.0 by default Jeff Layton
2025-10-08 20:13 ` [PATCH 2/2] nfsdctl: " Jeff Layton
2026-01-09 19:04 ` Jeff Layton [this message]
2026-01-10 9:20 ` [PATCH 0/2] nfsd/nfsdctl: default to starting with v4.0 servers disabled Steve Dickson
2026-03-22 20:30 ` Steve Dickson
2026-03-22 21:31 ` Salvatore Bonaccorso
2026-03-22 21:42 ` Jeff Layton
2026-03-23 7:02 ` salvatore.bonaccorso
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=d71e37c054c51428f34a51b6a980a62bc07a68e7.camel@kernel.org \
--to=jlayton@kernel.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