On Mon, Sep 14, 2009 at 05:16:22PM -0400, Trond Myklebust wrote: > On Mon, 2009-09-14 at 17:09 -0400, Trond Myklebust wrote: > > > I suppose we could. Alternatively, why not just call it once and for all > > when you start the NFSv4 server? The one cred will work on all > > rpc_clients. > > (This is correct...) > > > You just have to remember to bump the reference count > > before using it in an RPC call... > > Oops! Sorry, this is incorrect. The RPC engine will take care of bumping > the ref count for you if necessary... OK, on another look: I create a generic cred with rpc_lookup_machine_cred(). The gss cred then gets created by something like: rpc_call_async rpc_run_task rpc_new_task rpc_init_task rpcauth_bindcred cred->cr_ops->crbind == generic_bind_cred gss_auth->au_ops->lookup_cred(auth, acred, 0) rpcauth_lookup_credcache(gss_auth, acred, 0) But rpcauth_lookup_credcache ends up calling cr_init (gss_cred_init) and waiting synchronously for the gss upcall. I want to avoid that. Should I be setting up the cred differently, or could the rpc task initialization process be tweaked somehow? (Or am I just misunderstanding the code?) --b. -- 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
