From: Bryan Schumaker <bjschuma@netapp.com>
To: "Adamson, Dros" <Weston.Adamson@netapp.com>
Cc: Boaz Harrosh <bharrosh@panasas.com>,
"Myklebust, Trond" <Trond.Myklebust@netapp.com>,
"<linux-nfs@vger.kernel.org>" <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH 1/2] NFS: dont allow minorversion= opt when vers != 4
Date: Thu, 02 Feb 2012 08:51:54 -0500 [thread overview]
Message-ID: <4F2A94FA.30603@netapp.com> (raw)
In-Reply-To: <BD47F92C-6031-4F3F-A715-8275C7399717@netapp.com>
On 02/01/12 18:07, Adamson, Dros wrote:
> On Feb 1, 2012, at 5:44 PM, Boaz Harrosh wrote:
>
>> On 02/01/2012 09:06 PM, Weston Andros Adamson wrote:
>>> Don't allow invalid 'vers' and 'minorversion' combinations in mount options,
>>> such as "vers=3,minorversion=1".
>>>
>>
>> Just my $0.017 I don't see the point in this.
>>
>> If vers==3 then minorversion is ignored, just like today.
>> What kind of extra protection does it buy us?
>
> No, minorversion is not ignored when vers=3.
But after mounting, does setting vers=3, minorversion=1 cause any change in NFS v3 behavior?
- Bryan
>
> Try an invalid (v4) minorversion:
>
> $ sudo mount -t nfs -o vers=3,minorversion=2 server:/export /mnt
> mount.nfs: an incorrect mount option was specified
> $ dmesg | tail -1
> [ 1734.758101] NFS: bad mount option value specified: minorversion=2
>
> I can understand why this was never a priority, but I find it quite confusing when version=3,minorversion=1 succeeds -- I've fat-fingered that more than a few times, started running tests and only later realized my mistake.
>
>>
>> But maybe it's just me
>>
>
> I know it's not just me who's been confused by this in the past :)
>
> -dros
>
>> Thanks
>> Boaz
>>
>>> Signed-off-by: Weston Andros Adamson <dros@netapp.com>
>>> ---
>>> %d -> %u for printing mnt->version.
>>>
>>> fs/nfs/super.c | 7 +++++++
>>> 1 files changed, 7 insertions(+), 0 deletions(-)
>>>
>>> diff --git a/fs/nfs/super.c b/fs/nfs/super.c
>>> index 8e210b2..b88e023 100644
>>> --- a/fs/nfs/super.c
>>> +++ b/fs/nfs/super.c
>>> @@ -1519,6 +1519,9 @@ static int nfs_parse_mount_options(char *raw,
>>> if (!sloppy && invalid_option)
>>> return 0;
>>>
>>> + if (mnt->minorversion && mnt->version != 4)
>>> + goto out_minorversion_mismatch;
>>> +
>>> /*
>>> * verify that any proto=/mountproto= options match the address
>>> * familiies in the addr=/mountaddr= options.
>>> @@ -1552,6 +1555,10 @@ out_invalid_address:
>>> out_invalid_value:
>>> printk(KERN_INFO "NFS: bad mount option value specified: %s\n", p);
>>> return 0;
>>> +out_minorversion_mismatch:
>>> + printk(KERN_INFO "NFS: mount option vers=%u does not support "
>>> + "minorversion=%u\n", mnt->version, mnt->minorversion);
>>> + return 0;
>>> out_nomem:
>>> printk(KERN_INFO "NFS: not enough memory to parse option\n");
>>> return 0;
>>
>
next prev parent reply other threads:[~2012-02-02 13:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-01 19:06 [PATCH 1/2] NFS: dont allow minorversion= opt when vers != 4 Weston Andros Adamson
2012-02-01 22:44 ` Boaz Harrosh
2012-02-01 23:07 ` Adamson, Dros
2012-02-02 13:51 ` Bryan Schumaker [this message]
2012-02-02 17:03 ` Adamson, Dros
2012-02-02 19:00 ` Bryan Schumaker
2012-02-02 20:14 ` Adamson, Dros
-- strict thread matches above, loose matches on Subject: below --
2012-02-01 19:00 Weston Andros Adamson
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=4F2A94FA.30603@netapp.com \
--to=bjschuma@netapp.com \
--cc=Trond.Myklebust@netapp.com \
--cc=Weston.Adamson@netapp.com \
--cc=bharrosh@panasas.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.