On Apr 21, 2008, at 8:00 PM, Trond Myklebust wrote:
On Mon, 2008-04-21 at 13:50 -0400, Chuck Lever wrote:
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.
That seems unfriendly. Is this server-side behavior mandated? Why
wouldn't the server just treat an extraneous context destruction
request as a successful no-op?
You definitely should include an explanation of this server-side
behavior in the documenting comment for gss_destroying_context.
RFC-2203 states that servers are supposed to silently discard requests
that they don't recognise (see section 5.3.3.1 - Context
Management), so
it is correct server behaviour.
Dropping the request to destroy a context is fine. Temporarily
fencing the client is what I was concerned about.
--
Chuck Lever
chuck[dot]lever[at]oracle[dot]com
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
