Description of problem:
exit(0) silenty reaps the gssd_k5_kt_princ struct, the in-memory
rpc.gssd cache which means that rpc.gssd will get a new TGT and TGS for
each upcall, ignoring a valid TGT in the kerberos credential cache.

Version-Release number of selected component (if applicable):


How reproducible:100%


Steps to Reproduce:
1.Export sec=krb5 share
2.mount NFSv4.1 kerberos krb5 share - the client will first use krb51 (for the EXCHANGE_ID) then krb5 for the mount point.
3.

Actual results: 
Each upcall contacts the KDC for a new TGT (AS-REQ) even though there is a valid TKT in the Kerberos credential cache. You will never see more than one TGS per TKT.

Expected results: rpc.gssd will re-use a valid TKT


Additional info:

This patch, submitted Aug 19, 2015 to Steve Dickson and linux-nfs.org fixes this problem.

rpc.gssd: Replace exit(0) by return in process_krb5_upcall

From: Andy Adamson <andros>

exit(0) silenty reaps the gssd_k5_kt_princ struct, the in-memory
rpc.gssd cache which means that rpc.gssd will get a new TGT and TGS for
each upcall, ignoring a valid TGT in the kerberos credential cache.

Signed-off-by: Andy Adamson <andros>
---
 utils/gssd/gssd_proc.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/utils/gssd/gssd_proc.c b/utils/gssd/gssd_proc.c
index 03afc8b..3fc7bba 100644
--- a/utils/gssd/gssd_proc.c
+++ b/utils/gssd/gssd_proc.c
@@ -684,7 +684,7 @@ out:
                AUTH_DESTROY(auth);
        if (rpc_clnt)
                clnt_destroy(rpc_clnt);
-       exit(0);
+       return;

 out_return_error:
        do_error_downcall(fd, uid, downcall_err);