Linux NFS development
 help / color / mirror / Atom feed
* [PATCH] NFS: Ignore transport protocol when detecting server trunking
@ 2015-01-03 19:45 Chuck Lever
  2015-01-03 21:20 ` Trond Myklebust
  0 siblings, 1 reply; 3+ messages in thread
From: Chuck Lever @ 2015-01-03 19:45 UTC (permalink / raw)
  To: trond.myklebust; +Cc: linux-nfs

Detect server trunking across transport protocols. Otherwise, an
RDMA mount and a TCP mount of the same server will end up with
separate nfs_clients using the same clientid4.

Reported-by: Dai Ngo <dai.ngo@oracle.com>
Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
---
Re: yesterday's discussion of "[PATCH] NFSv4.1: Fix client id
trunking on Linux". This patch seems to address the behavior I
mentioned.

 fs/nfs/nfs4client.c |    6 ------
 1 file changed, 6 deletions(-)

diff --git a/fs/nfs/nfs4client.c b/fs/nfs/nfs4client.c
index c0fe338..c7bc38e 100644
--- a/fs/nfs/nfs4client.c
+++ b/fs/nfs/nfs4client.c
@@ -540,9 +540,6 @@ int nfs40_walk_client_list(struct nfs_client *new,
 		if (pos->rpc_ops != new->rpc_ops)
 			continue;
 
-		if (pos->cl_proto != new->cl_proto)
-			continue;
-
 		if (pos->cl_minorversion != new->cl_minorversion)
 			continue;
 
@@ -675,9 +672,6 @@ int nfs41_walk_client_list(struct nfs_client *new,
 		if (pos->rpc_ops != new->rpc_ops)
 			continue;
 
-		if (pos->cl_proto != new->cl_proto)
-			continue;
-
 		if (pos->cl_minorversion != new->cl_minorversion)
 			continue;
 


^ permalink raw reply related	[flat|nested] 3+ messages in thread

* Re: [PATCH] NFS: Ignore transport protocol when detecting server trunking
  2015-01-03 19:45 [PATCH] NFS: Ignore transport protocol when detecting server trunking Chuck Lever
@ 2015-01-03 21:20 ` Trond Myklebust
  2015-01-03 21:23   ` Chuck Lever
  0 siblings, 1 reply; 3+ messages in thread
From: Trond Myklebust @ 2015-01-03 21:20 UTC (permalink / raw)
  To: Chuck Lever; +Cc: Linux NFS Mailing List

On Sat, Jan 3, 2015 at 2:45 PM, Chuck Lever <chuck.lever@oracle.com> wrote:
> Detect server trunking across transport protocols. Otherwise, an
> RDMA mount and a TCP mount of the same server will end up with
> separate nfs_clients using the same clientid4.
>
> Reported-by: Dai Ngo <dai.ngo@oracle.com>
> Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
> ---
> Re: yesterday's discussion of "[PATCH] NFSv4.1: Fix client id
> trunking on Linux". This patch seems to address the behavior I
> mentioned.
>
>  fs/nfs/nfs4client.c |    6 ------
>  1 file changed, 6 deletions(-)
>
> diff --git a/fs/nfs/nfs4client.c b/fs/nfs/nfs4client.c
> index c0fe338..c7bc38e 100644
> --- a/fs/nfs/nfs4client.c
> +++ b/fs/nfs/nfs4client.c
> @@ -540,9 +540,6 @@ int nfs40_walk_client_list(struct nfs_client *new,
>                 if (pos->rpc_ops != new->rpc_ops)
>                         continue;
>
> -               if (pos->cl_proto != new->cl_proto)
> -                       continue;
> -
>                 if (pos->cl_minorversion != new->cl_minorversion)
>                         continue;
>
> @@ -675,9 +672,6 @@ int nfs41_walk_client_list(struct nfs_client *new,
>                 if (pos->rpc_ops != new->rpc_ops)
>                         continue;
>
> -               if (pos->cl_proto != new->cl_proto)
> -                       continue;
> -
>                 if (pos->cl_minorversion != new->cl_minorversion)
>                         continue;
>
>

Yep. Sorry, I only noticed this after I'd written my own version. I'll
replace mine with this one.


-- 
Trond Myklebust
Linux NFS client maintainer, PrimaryData
trond.myklebust@primarydata.com

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [PATCH] NFS: Ignore transport protocol when detecting server trunking
  2015-01-03 21:20 ` Trond Myklebust
@ 2015-01-03 21:23   ` Chuck Lever
  0 siblings, 0 replies; 3+ messages in thread
From: Chuck Lever @ 2015-01-03 21:23 UTC (permalink / raw)
  To: Trond Myklebust; +Cc: Linux NFS Mailing List


On Jan 3, 2015, at 4:20 PM, Trond Myklebust <trond.myklebust@primarydata.com> wrote:

> On Sat, Jan 3, 2015 at 2:45 PM, Chuck Lever <chuck.lever@oracle.com> wrote:
>> Detect server trunking across transport protocols. Otherwise, an
>> RDMA mount and a TCP mount of the same server will end up with
>> separate nfs_clients using the same clientid4.
>> 
>> Reported-by: Dai Ngo <dai.ngo@oracle.com>
>> Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
>> ---
>> Re: yesterday's discussion of "[PATCH] NFSv4.1: Fix client id
>> trunking on Linux". This patch seems to address the behavior I
>> mentioned.
>> 
>> fs/nfs/nfs4client.c |    6 ------
>> 1 file changed, 6 deletions(-)
>> 
>> diff --git a/fs/nfs/nfs4client.c b/fs/nfs/nfs4client.c
>> index c0fe338..c7bc38e 100644
>> --- a/fs/nfs/nfs4client.c
>> +++ b/fs/nfs/nfs4client.c
>> @@ -540,9 +540,6 @@ int nfs40_walk_client_list(struct nfs_client *new,
>>                if (pos->rpc_ops != new->rpc_ops)
>>                        continue;
>> 
>> -               if (pos->cl_proto != new->cl_proto)
>> -                       continue;
>> -
>>                if (pos->cl_minorversion != new->cl_minorversion)
>>                        continue;
>> 
>> @@ -675,9 +672,6 @@ int nfs41_walk_client_list(struct nfs_client *new,
>>                if (pos->rpc_ops != new->rpc_ops)
>>                        continue;
>> 
>> -               if (pos->cl_proto != new->cl_proto)
>> -                       continue;
>> -
>>                if (pos->cl_minorversion != new->cl_minorversion)
>>                        continue;
>> 
>> 
> 
> Yep. Sorry, I only noticed this after I'd written my own version. I'll
> replace mine with this one.

Thanks, much appreciated!

--
Chuck Lever
chuck[dot]lever[at]oracle[dot]com




^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2015-01-03 21:23 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2015-01-03 19:45 [PATCH] NFS: Ignore transport protocol when detecting server trunking Chuck Lever
2015-01-03 21:20 ` Trond Myklebust
2015-01-03 21:23   ` Chuck Lever

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox