All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steve Dickson <SteveD@RedHat.com>
To: Trond Myklebust <trondmy@primarydata.com>
Cc: James Bruce Fields <bfields@fieldses.org>,
	"neilb@suse.com" <neilb@suse.com>,
	Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH 1/2] nfsd: Allow the caller to turn off NFSv4.0 without turning off NFSv4.x
Date: Tue, 4 Apr 2017 17:31:56 -0400	[thread overview]
Message-ID: <4a409f78-9dfb-cfa4-67e7-6c67b8d263ac@RedHat.com> (raw)
In-Reply-To: <4B984CF4-7D50-4B11-B26E-886845068329@primarydata.com>



On 04/04/2017 05:11 PM, Trond Myklebust wrote:
> 
>> On Apr 4, 2017, at 17:07, Steve Dickson <SteveD@RedHat.com <mailto:SteveD@RedHat.com>> wrote:
>>
>>
>>
>> On 04/04/2017 04:26 PM, Trond Myklebust wrote:
>>> On Tue, 2017-04-04 at 16:07 -0400, Steve Dickson wrote:
>>>> Hey Trond,
>>>>
>>>> My apologies for taking so long to address this... 
>>>>
>>>> On 02/23/2017 07:33 PM, Trond Myklebust wrote:
>>>>> The new semantic is that '-N4' turns off all NFSv4 minor versions,
>>>>> while
>>>>> '-V4' turns them all on. In order to turn off just minor version x
>>>>> (x >= 0),
>>>>> use -N4.x, and to turn it back on. '-V4.x'.
>>>>>
>>>>> Note that on older kernels, attempting to use -N4.0 and -V4.0 is
>>>>> equivalent to specifying -N4 or -V4.
>>>>
>>>> doing a 
>>>>
>>>> nfsd -d -N4.0 -V4.1 -V4.2 
>>>> nfsd: Writing version string to kernel: -2 +3 -4 +4.1 +4.2
>>>>
>>>> does the right thing but when I do a
>>>>
>>>> nfsd -d -N4.0 
>>>> nfsd: Writing version string to kernel: -2 +3 -4
>>>>
>>>> It brings down all of the v4 minor versions, Is that
>>>> intentional? It seems to me doing a -N4.0 should only
>>>> stop 4.0 from coming up not v4.1 or v4.2
>>>
>>> That is unfortunately not possible for older kernels. They lack the
>>> kernel API to turn off NFSv4.0 only. We could perhaps try to return an
>>> error if you were to specify these flags for those kernels, but that
>>> would require us to hard-code a "minimal" kernel version in nfs-utils.
>> Well we already do that in the legacy mounting code to figure out
>> what mount version to use, but looking at that code it would be pain
>> to pull it out. 
>>
>> But I'm thinking the expectation of nfsd -N4.0 is to only 
>> turn off v4.0 and not work the same as -N4 which turns all of
>> v4 off which is expected. 
>>
>> When you say old kernel... How old?
> 
> Linux 4.10 or older.
So what will happen when this is done
    nfsd -d -N4.0 -V4.1 -V4.2
on an older kernel?

Also looking at the code when -N4.0 is used
it zero out the entire minorversset which means 
the -4.1 and -4.2 is not written out to the versions file

nfsd -d -N4
nfsd: Writing version string to kernel: -2 +3 -4 -4.1 -4.2

nfsd -d -N4.0
nfsd: Writing version string to kernel: -2 +3 -4

I'm not sure if this matters or not... but it is different.

steved.

  parent reply	other threads:[~2017-04-04 21:31 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-24  0:33 [PATCH 0/2] Patch rpc.nfsd to allow the caller to turn off NFSv4.0 Trond Myklebust
2017-02-24  0:33 ` [PATCH 1/2] nfsd: Allow the caller to turn off NFSv4.0 without turning off NFSv4.x Trond Myklebust
2017-02-24  0:33   ` [PATCH 2/2] nfsd: Change the default to enable all minor versions unless told otherwise Trond Myklebust
2017-02-24  1:17     ` NeilBrown
2017-02-24  1:42       ` Trond Myklebust
2017-02-24  2:27         ` NeilBrown
2017-02-24 20:32           ` bfields
2017-04-04 20:08     ` Steve Dickson
2017-04-04 20:07   ` [PATCH 1/2] nfsd: Allow the caller to turn off NFSv4.0 without turning off NFSv4.x Steve Dickson
2017-04-04 20:26     ` Trond Myklebust
2017-04-04 21:07       ` Steve Dickson
     [not found]         ` <4B984CF4-7D50-4B11-B26E-886845068329@primarydata.com>
2017-04-04 21:31           ` Steve Dickson [this message]
2017-04-05 17:29             ` 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=4a409f78-9dfb-cfa4-67e7-6c67b8d263ac@RedHat.com \
    --to=steved@redhat.com \
    --cc=bfields@fieldses.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=neilb@suse.com \
    --cc=trondmy@primarydata.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.