All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chuck Lever <chuck.lever@oracle.com>
To: Trond Myklebust <trond.myklebust@primarydata.com>
Cc: Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH] NFSv4.1: Fix client id trunking on Linux
Date: Fri, 2 Jan 2015 16:44:43 -0500	[thread overview]
Message-ID: <7BF7AAE6-8DE2-4664-AFFB-6A84F51F97DC@oracle.com> (raw)
In-Reply-To: <1420234772-13083-1-git-send-email-trond.myklebust@primarydata.com>


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

> Currently, our trunking code will check for session trunking, but will
> fail to detect client id trunking. This is a problem, because it means
> that the client will fail to recognise that the two connections represent
> shared state, even if they do not permit a shared session.
> By removing the check for the server minor id, and only checking the
> major id, we will end up doing the right thing in both cases: we close
> down the new nfs_client and fall back to using the existing one.

Fair enough.

Does this detect the case where two concurrent NFSv4.1 mounts
of the same server use different transport protocols?


> Fixes: 05f4c350ee02e ("NFS: Discover NFSv4 server trunking when mounting")
> Cc: Chuck Lever <chuck.lever@oracle.com>
> Cc: stable@vger.kernel.org # 3.7.x
> Signed-off-by: Trond Myklebust <trond.myklebust@primarydata.com>
> ---
> fs/nfs/nfs4client.c | 17 ++++++++---------
> 1 file changed, 8 insertions(+), 9 deletions(-)
> 
> diff --git a/fs/nfs/nfs4client.c b/fs/nfs/nfs4client.c
> index 03311259b0c4..d949d0f378ec 100644
> --- a/fs/nfs/nfs4client.c
> +++ b/fs/nfs/nfs4client.c
> @@ -566,20 +566,14 @@ static bool nfs4_match_clientids(struct nfs_client *a, struct nfs_client *b)
> }
> 
> /*
> - * Returns true if the server owners match
> + * Returns true if the server major ids match
>  */
> static bool
> -nfs4_match_serverowners(struct nfs_client *a, struct nfs_client *b)
> +nfs4_check_clientid_trunking(struct nfs_client *a, struct nfs_client *b)
> {
> 	struct nfs41_server_owner *o1 = a->cl_serverowner;
> 	struct nfs41_server_owner *o2 = b->cl_serverowner;
> 
> -	if (o1->minor_id != o2->minor_id) {
> -		dprintk("NFS: --> %s server owner minor IDs do not match\n",
> -			__func__);
> -		return false;
> -	}
> -
> 	if (o1->major_id_sz != o2->major_id_sz)
> 		goto out_major_mismatch;
> 	if (memcmp(o1->major_id, o2->major_id, o1->major_id_sz) != 0)
> @@ -654,7 +648,12 @@ int nfs41_walk_client_list(struct nfs_client *new,
> 		if (!nfs4_match_clientids(pos, new))
> 			continue;
> 
> -		if (!nfs4_match_serverowners(pos, new))
> +		/*
> +		 * Note that session trunking is just a special subcase of
> +		 * client id trunking. In either case, we want to fall back
> +		 * to using the existing nfs_client.
> +		 */
> +		if (!nfs4_check_clientid_trunking(pos, new))
> 			continue;
> 
> 		atomic_inc(&pos->cl_count);
> -- 
> 2.1.0
> 

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




  reply	other threads:[~2015-01-02 21:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-02 21:39 [PATCH] NFSv4.1: Fix client id trunking on Linux Trond Myklebust
2015-01-02 21:44 ` Chuck Lever [this message]
2015-01-02 22:09   ` Trond Myklebust
2015-01-02 23:36     ` Chuck Lever
2015-01-03 21:19       ` Trond Myklebust
2015-01-03 19:45 ` Chuck Lever

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=7BF7AAE6-8DE2-4664-AFFB-6A84F51F97DC@oracle.com \
    --to=chuck.lever@oracle.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=trond.myklebust@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.