All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steve Dickson <SteveD@redhat.com>
To: "Myklebust, Trond" <Trond.Myklebust@netapp.com>
Cc: Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: [RFC PATCH V2] mount: Added the -o v4.1 mount option
Date: Mon, 19 Nov 2012 11:14:12 -0500	[thread overview]
Message-ID: <50AA5AD4.5070808@RedHat.com> (raw)
In-Reply-To: <4FA345DA4F4AE44899BD2B03EEEC2FA9092EEFD7@SACEXCMBX04-PRD.hq.netapp.com>



On 19/11/12 11:02, Myklebust, Trond wrote:
> On Mon, 2012-11-19 at 10:58 -0500, Steve Dickson wrote:
>>
>> On 19/11/12 10:54, Myklebust, Trond wrote:
>>> On Mon, 2012-11-19 at 10:43 -0500, Steve Dickson wrote:
>>>> This patch will convert -o v4.1, vers=4.1 or nfsvers=4.1 into
>>>> the corresponding "v4,minorversion=1", "vers=4,minorversion=1"
>>>> or "nfsvers=4,minorversion=1" options.
>>>>
>>>
>>> NACK.
>>>
>>> If you are going to do this, then please do it only for kernels that
>>> don't support the "vers=4.1" syntax. i.e. anything older than Linux-3.4.
>> This is the intention... 
>>
>>>
>>> We want to get rid of minorversion=x, not perpetuate it...
>>>
>> Understood... But that is not option in some worlds... ;-) 
> 
> Sure it is. The mount program can continue to parse minorversion= after
> it is gone from the kernel and convert it into the vers=4.x syntax.
> 
Basically what I'm doing now, with the exception of not adding
the minorversion=1 options... 

BTW, there is a bug in the -o v4.1 current logic... 

mount -o v4.1 produces both "v4.1,vers=4,..." in the string that given
to the kernel which does not seem right... I would assume just a "v4.1,.."
should be pumped down.. 

steved.

  reply	other threads:[~2012-11-19 16:14 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-19 15:43 [RFC PATCH V2] mount: Added the -o v4.1 mount option Steve Dickson
2012-11-19 15:54 ` Myklebust, Trond
2012-11-19 15:58   ` Steve Dickson
2012-11-19 16:02     ` Myklebust, Trond
2012-11-19 16:14       ` Steve Dickson [this message]
2012-11-19 16:24         ` Myklebust, Trond
2012-11-19 18:11           ` Chuck Lever
2012-11-19 18:29             ` Myklebust, Trond
2012-11-19 18:39               ` Chuck Lever
2012-11-19 19:04                 ` Myklebust, Trond
2012-11-19 21:15                   ` J. Bruce Fields
2012-11-19 21:40               ` Steve Dickson
2012-11-19 18:21 ` Chuck Lever
2012-11-19 21:51   ` 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=50AA5AD4.5070808@RedHat.com \
    --to=steved@redhat.com \
    --cc=Trond.Myklebust@netapp.com \
    --cc=linux-nfs@vger.kernel.org \
    /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.