SUNRPC: Don't attempt to destroy expired RPCSEC_GSS credentials..
authorTrond Myklebust <Trond.Myklebust@netapp.com>
Sat, 19 Apr 2008 18:22:31 +0000 (14:22 -0400)
committerTrond Myklebust <Trond.Myklebust@netapp.com>
Sat, 19 Apr 2008 20:52:54 +0000 (16:52 -0400)
commit080a1f148df0615f7a610e4776dd8f3fb706f54f
treebf6f52a5a2974adee916c86a01ffdd3a739cf71f
parentb6ddf64ffe9d59577a9176856bb6fe69a539f573
SUNRPC: Don't attempt to destroy expired RPCSEC_GSS credentials..

..and always destroy using a 'soft' RPC call. Destroying GSS credentials
isn't mandatory; the server can always cope with a few credentials not
getting destroyed in a timely fashion.

This actually fixes a hang situation. Basically, some servers will decide
that the client is crazy if it tries to destroy an RPC context for which
they have sent an RPCSEC_GSS_CREDPROBLEM, and so will refuse to talk to it
for a while.
The regression therefor probably was introduced by commit
0df7fb74fbb709591301871a38aac7735a1d6583.

Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
net/sunrpc/auth_gss/auth_gss.c