linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Boaz Harrosh <bharrosh@panasas.com>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: Weston Andros Adamson <dros@netapp.com>,
	<Trond.Myklebust@netapp.com>, <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH] NFS: add mount options 'v4.0' and 'v4.1'
Date: Tue, 7 Feb 2012 20:21:56 +0200	[thread overview]
Message-ID: <4F316BC4.4030504@panasas.com> (raw)
In-Reply-To: <A5356E85-1E22-4C4C-A30C-58A912AE3C9F@oracle.com>

On 02/07/2012 06:59 PM, Chuck Lever wrote:
> Hi-
> 
> On Feb 7, 2012, at 11:49 AM, Weston Andros Adamson wrote:
>> 
>> NFS: add mount options 'v4.0' and 'v4.1'

Good god thanks, that'll be nice.

Why did we have to suffer for 5 years without it? ;-)

>> Signed-off-by: Weston Andros Adamson <dros@netapp.com>
>> ---
>> Updated to add 'v4.0' as trond requested.
>>
>> We'll talk about this change at connectathon.
>>
>> This 'just works' with mount.nfs(8) -- v.* options are passed to the 
>> kernel with no modifications needed.
> 
> I'm more concerned about version auto-negotation.
> 

If we are at it can we also have a "this-version-only" option which
disables "auto-negotation"

I know that's an hard one

OK we'll talk at CON12.

Thanks Andy
Boaz

>>
>> fs/nfs/super.c |   14 +++++++++++++-
>> 1 files changed, 13 insertions(+), 1 deletions(-)
>>
>> diff --git a/fs/nfs/super.c b/fs/nfs/super.c
>> index b88e023..d89cee2 100644
>> --- a/fs/nfs/super.c
>> +++ b/fs/nfs/super.c
>> @@ -80,7 +80,7 @@ enum {
>> 	Opt_cto, Opt_nocto,
>> 	Opt_ac, Opt_noac,
>> 	Opt_lock, Opt_nolock,
>> -	Opt_v2, Opt_v3, Opt_v4,
>> +	Opt_v2, Opt_v3, Opt_v4, Opt_v4_0, Opt_v4_1,
>> 	Opt_udp, Opt_tcp, Opt_rdma,
>> 	Opt_acl, Opt_noacl,
>> 	Opt_rdirplus, Opt_nordirplus,
>> @@ -136,6 +136,8 @@ static const match_table_t nfs_mount_option_tokens = {
>> 	{ Opt_v2, "v2" },
>> 	{ Opt_v3, "v3" },
>> 	{ Opt_v4, "v4" },
>> +	{ Opt_v4_0, "v4.0" },
>> +	{ Opt_v4_1, "v4.1" },
>> 	{ Opt_udp, "udp" },
>> 	{ Opt_tcp, "tcp" },
>> 	{ Opt_rdma, "rdma" },
>> @@ -1172,6 +1174,16 @@ static int nfs_parse_mount_options(char *raw,
>> 			mnt->flags &= ~NFS_MOUNT_VER3;
>> 			mnt->version = 4;
>> 			break;
>> +		case Opt_v4_0:
>> +			mnt->flags &= ~NFS_MOUNT_VER3;
>> +			mnt->version = 4;
>> +			mnt->minorversion = 0;
>> +			break;
>> +		case Opt_v4_1:
>> +			mnt->flags &= ~NFS_MOUNT_VER3;
>> +			mnt->version = 4;
>> +			mnt->minorversion = 1;
>> +			break;
>> 		case Opt_udp:
>> 			mnt->flags &= ~NFS_MOUNT_TCP;
>> 			mnt->nfs_server.protocol = XPRT_TRANSPORT_UDP;
>> -- 
>> 1.7.4.4
>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 


  reply	other threads:[~2012-02-07 18:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-07 16:49 [PATCH] NFS: add mount options 'v4.0' and 'v4.1' Weston Andros Adamson
2012-02-07 16:59 ` Chuck Lever
2012-02-07 18:21   ` Boaz Harrosh [this message]
2012-02-07 18:30     ` Adamson, Dros
2012-02-07 18:41       ` Myklebust, Trond
2012-02-07 18:48         ` Myklebust, Trond
2012-02-07 19:05           ` Steve Dickson
2012-02-07 18:37     ` Chuck Lever
2012-02-07 18:41       ` Boaz Harrosh

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=4F316BC4.4030504@panasas.com \
    --to=bharrosh@panasas.com \
    --cc=Trond.Myklebust@netapp.com \
    --cc=chuck.lever@oracle.com \
    --cc=dros@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).