public inbox for linux-nfs@vger.kernel.org
 help / color / mirror / Atom feed
From: salvatore.bonaccorso@gmail.com
To: Jeff Layton <jlayton@kernel.org>
Cc: Steve Dickson <steved@redhat.com>, linux-nfs@vger.kernel.org
Subject: Re: [PATCH 0/2] nfsd/nfsdctl: default to starting with v4.0 servers disabled
Date: Mon, 23 Mar 2026 08:02:52 +0100	[thread overview]
Message-ID: <acDlnPo3z5Uk2vcH@eldamar.lan> (raw)
In-Reply-To: <643b2d6bb1bdda8c2602535da9c679e6dfbe68a7.camel@kernel.org>

Hi Jeff,

On Sun, Mar 22, 2026 at 05:42:29PM -0400, Jeff Layton wrote:
> On Sun, 2026-03-22 at 22:31 +0100, Salvatore Bonaccorso wrote:
> > Hi Steve, Jeff,
> > 
> > On Sun, Mar 22, 2026 at 04:30:02PM -0400, Steve Dickson wrote:
> > > 
> > > 
> > > On 10/8/25 4:13 PM, 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,
> > > Committed... (tag: nfs-utils-2-9-1-rc1)
> > > 
> > > My apologies for taking so long... The CVE
> > > took longer than expected and there was
> > > some issues with recent patches,
> > > which caused another release..
> > > 
> > > Turning off a protocol version (v4.0)
> > > on the server by default which this rc
> > > release does, is not a small thing
> > > although with the 7.X kernels the
> > > v4.0 client is already off.
> > 
> > I have one small followup question on that. The nfs.conf reads:
> > 
> > [nfsd]
> > # debug=0
> > # threads=16
> > # host=
> > # port=0
> > # grace-time=90
> > # lease-time=90
> > # udp=n
> > # tcp=y
> > # vers3=y
> > # vers4=y
> > # vers4.0=y
> > # vers4.1=y
> > # vers4.2=y
> > [...]
> > 
> > Should the 'default off' change as well be reflected in the commented
> > entry for vers4.0 and read vers4.0=n for consistency?
> > 
> 
> Yes, good catch. Would you mind spinning up a patch? If not, I'll do
> one in the near future.

Thanks for confirming, yes happy to provide a patch for that, will
send it later the day.

Regards,
Salvatore

      reply	other threads:[~2026-03-23  7:02 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 ` [PATCH 0/2] nfsd/nfsdctl: default to starting with v4.0 servers disabled Jeff Layton
2026-01-10  9:20   ` 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 [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=acDlnPo3z5Uk2vcH@eldamar.lan \
    --to=salvatore.bonaccorso@gmail.com \
    --cc=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