From: <andros@netapp.com>
To: <trond.myklebust@netapp.com>
Cc: <linux-nfs@vger.kernel.org>, Andy Adamson <andros@netapp.com>
Subject: [PATCH 1/4] NFSv4.1 Use the mount point rpc_clnt for layoutreturn
Date: Mon, 22 Jul 2013 12:42:05 -0400 [thread overview]
Message-ID: <1374511328-49579-1-git-send-email-andros@netapp.com> (raw)
From: Andy Adamson <andros@netapp.com>
Should not use the clientid maintenance rpc_clnt.
Signed-off-by: Andy Adamson <andros@netapp.com>
---
fs/nfs/nfs4proc.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/nfs/nfs4proc.c b/fs/nfs/nfs4proc.c
index cf11799..7a846b6 100644
--- a/fs/nfs/nfs4proc.c
+++ b/fs/nfs/nfs4proc.c
@@ -6876,7 +6876,7 @@ int nfs4_proc_layoutreturn(struct nfs4_layoutreturn *lrp)
.rpc_cred = lrp->cred,
};
struct rpc_task_setup task_setup_data = {
- .rpc_client = lrp->clp->cl_rpcclient,
+ .rpc_client = NFS_SERVER(lrp->args.inode)->client,
.rpc_message = &msg,
.callback_ops = &nfs4_layoutreturn_call_ops,
.callback_data = lrp,
--
1.8.3.1
next reply other threads:[~2013-07-22 16:42 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-22 16:42 andros [this message]
2013-07-22 16:42 ` [PATCH 2/4] NFSv4.1 Use clientid management rpc_clnt for fs_locations andros
2013-08-07 16:54 ` Myklebust, Trond
[not found] ` <479EB531-9CD2-42E2-AB98-A3CD9B13603D@netapp.com>
2013-08-07 18:04 ` Myklebust, Trond
2013-08-07 18:19 ` Myklebust, Trond
2013-08-07 18:24 ` Adamson, Andy
2013-08-07 18:28 ` Fwd: " Adamson, Andy
2013-08-07 18:32 ` Myklebust, Trond
2013-08-07 18:32 ` Adamson, Andy
2013-08-07 18:36 ` Myklebust, Trond
2013-07-22 16:42 ` [PATCH 3/4] NFSv4.1 Use clientid management rpc_clnt for secinfo andros
2013-07-22 16:58 ` Myklebust, Trond
2013-07-22 17:14 ` Adamson, Andy
2013-08-07 16:57 ` Myklebust, Trond
2013-07-22 16:42 ` [PATCH 4/4] NFSv4.1 Use clientid management rpc_clnt for secinfo_no_name andros
2013-08-07 16:58 ` Myklebust, Trond
2013-07-22 16:44 ` [PATCH 1/4] NFSv4.1 Use the mount point rpc_clnt for layoutreturn Myklebust, Trond
2013-07-22 16:46 ` Myklebust, Trond
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=1374511328-49579-1-git-send-email-andros@netapp.com \
--to=andros@netapp.com \
--cc=linux-nfs@vger.kernel.org \
--cc=trond.myklebust@netapp.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.