From: <andros@netapp.com>
To: <trond.myklebust@netapp.com>
Cc: <linux-nfs@vger.kernel.org>, Andy Adamson <andros@netapp.com>
Subject: [PATCH Version 2 5/5] SUNRPC add EKEYEXPIRED case to call_bind_status
Date: Tue, 22 Oct 2013 10:21:16 -0400 [thread overview]
Message-ID: <1382451676-2963-6-git-send-email-andros@netapp.com> (raw)
In-Reply-To: <1382451676-2963-1-git-send-email-andros@netapp.com>
From: Andy Adamson <andros@netapp.com>
Signed-off-by: Andy Adamson <andros@netapp.com>
---
net/sunrpc/clnt.c | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/net/sunrpc/clnt.c b/net/sunrpc/clnt.c
index 7352aef..8a5c5b6 100644
--- a/net/sunrpc/clnt.c
+++ b/net/sunrpc/clnt.c
@@ -1622,6 +1622,11 @@ call_bind_status(struct rpc_task *task)
dprintk("RPC: %5u unrecognized remote rpcbind service\n",
task->tk_pid);
break;
+ case -EKEYEXPIRED:
+ /* credential key has expired */
+ dprintk("RPC: %5u Credential key has expired\n",
+ task->tk_pid);
+ break;
case -EPROTONOSUPPORT:
dprintk("RPC: %5u remote rpcbind version unavailable, retrying\n",
task->tk_pid);
--
1.8.3.1
prev parent reply other threads:[~2013-10-22 14:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-22 14:21 [PATCH Version 2 0/5] SUNRPC: destroy gss_cred and context on Kerberos credential destruction andros
2013-10-22 14:21 ` [PATCH Version 2 1/5] SUNRPC: register the gss-ctx key type andros
2013-10-22 14:21 ` [PATCH Version 2 2/5] SUNRPC set gss_cred gss-ctx key serial andros
2013-10-22 14:21 ` [PATCH Version 2 3/5] SUNRPC: invalidate gss_context upon gss-ctx keyring key destruction andros
2013-10-28 22:14 ` Myklebust, Trond
2013-10-22 14:21 ` [PATCH Version 2 4/5] SUNRPC: allow only existing buffered writes on creds with destroyed keys andros
2013-10-22 14:21 ` andros [this message]
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=1382451676-2963-6-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 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).