Chuck Lever da35187801 [PATCH] RPC: proper soft timeout behavior for rpcbind ... Implement a best practice: for soft mounts, an rpcbind timeout should cause an RPC request to fail. This also provides an FSM hook for retrying an rpcbind with a different rpcbind protocol version. We'll use this later to try multiple rpcbind protocol versions when binding. To enable this, expose the RPC error code returned during a portmap request to the FSM so it can make some decision about how to report, retry, or fail the request. Test-plan: Hundreds of passes with connectathon NFSv3 locking suite, on the client and server. Version: Thu, 11 Aug 2005 16:01:53 -0400 Signed-off-by: Chuck Lever <cel@netapp.com> Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>		2005-09-23 12:38:04 -04:00
..
auth_gss
auth_null.c
auth_unix.c
auth.c
cache.c
clnt.c	[PATCH] RPC: proper soft timeout behavior for rpcbind	2005-09-23 12:38:04 -04:00
Makefile
pmap_clnt.c
rpc_pipe.c
sched.c
stats.c
sunrpc_syms.c
svc.c
svcauth_unix.c
svcauth.c
svcsock.c
sysctl.c
timer.c
xdr.c
xprt.c	[PATCH] RPC: Report connection errors properly when mounting with "soft"	2005-09-23 12:38:03 -04:00