From: Scott Mayhew <smayhew@redhat.com>
To: steved@redhat.com
Cc: linux-nfs@vger.kernel.org
Subject: [nfs-utils PATCH 0/2] A few fixes to rpc.nfsd enabling/disabling minor version 0
Date: Fri, 10 Aug 2018 16:44:19 -0400 [thread overview]
Message-ID: <20180810204421.21882-1-smayhew@redhat.com> (raw)
The first patch allows version 4.0 to be enabled/disabled via the
nfs.conf file.
The second patch adds a variable to track when the user explicitly
requested version 4.0 to be enabled/disabled so that '+4.0' or '-4.0'
can be written to /proc/fs/nfsd/versions on 4.11 (first appearance of
commit d3635ff07e8c "nfsd: fix configuration of supported minor
versions").
Note that if version 4.0 is disabled (either via '-N4.0' on the command
line or via 'vers4.0=n' in nfs.conf), then it must be re-enabled
explicitly (either via '-V4.0' on the command line or via 'vers4.0=y' in
nfs.conf). Simply removing the '-N4.0'/'vers4.0=n' options and/or
replacing them with '-V4/vers4=y' is not sufficient. It is my
understanding that that is the desired behavior.
Scott Mayhew (2):
nfsd: allow verson 4.0 to be enabled/disabled via nfs.conf
nfsd: track when the user explicitly requested version 4.0
utils/nfsd/nfsd.c | 17 +++++++++++------
utils/nfsd/nfssvc.c | 14 +++++++++-----
utils/nfsd/nfssvc.h | 3 ++-
3 files changed, 22 insertions(+), 12 deletions(-)
--
2.14.4
next reply other threads:[~2018-08-10 23:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-10 20:44 Scott Mayhew [this message]
2018-08-10 20:44 ` [nfs-utils PATCH 1/2] nfsd: allow verson 4.0 to be enabled/disabled via nfs.conf Scott Mayhew
2018-08-10 20:44 ` [nfs-utils PATCH 2/2] nfsd: track when the user explicitly requested version 4.0 Scott Mayhew
2018-08-20 13:00 ` [nfs-utils PATCH 0/2] A few fixes to rpc.nfsd enabling/disabling minor version 0 Steve Dickson
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=20180810204421.21882-1-smayhew@redhat.com \
--to=smayhew@redhat.com \
--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 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.