Consider this patch a RFC at this point. This changes how the
use-gss-proxy file works, and alters the kernel upcall to delay a little
bit before giving up on it if gssproxy isn't up yet.
It's not heavily tested yet, but it seems to do the right thing...
I think the first patch isn't too controversial. The big question is
whether the initial upcall delay is desirable.
Thoughts?
Jeff Layton (5):
sunrpc: don't wait for write before allowing reads from use-gss-proxy
file
sunrpc: don't hang indefinitely in wait_for_gss_proxy
sunrpc: wait for gssproxy to start on initial upcall attempt before
falling back to legacy upcall
sunrpc: fix potential race between setting use_gss_proxy and the
upcall rpc_clnt
sunrpc: allow gssproxy to be explicitly disabled from userland
net/sunrpc/auth_gss/svcauth_gss.c | 72 +++++++++++++++++++++------------------
1 file changed, 39 insertions(+), 33 deletions(-)
--
1.8.4.2
--
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
