On 11/11/13 13:25, Myklebust, Trond wrote: > > On Nov 11, 2013, at 13:06, Steve Dickson <SteveD@xxxxxxxxxx> wrote: > >> >> >> On 09/11/13 18:12, Myklebust, Trond wrote: >>> One alternative to the above scheme, which I believe that I’ve >>> suggested before, is to have a permanent entry in rpc_pipefs >>> that rpc.gssd can open and that the kernel can use to detect >>> that it is running. If we make it /var/lib/nfs/rpc_pipefs/gssd/clnt00/gssd, >>> then AFAICS we don’t need to change nfs-utils at all, since all newer >>> versions of rpc.gssd will try to open for read anything of the form >>> /var/lib/nfs/rpc_pipefs/*/clntXX/gssd... >> >> After further review I am going going have to disagree with you on this. >> Since all the context is cached on the initial mount the kernel > > What context? The krb5 blob that the kernel is call up to rpc.gssd to get.. Maybe I'm using the wrong terminology??? > >> should be using the call_usermodehelper() to call up to rpc.gssd >> to get the context, which means we could put this upcall noise >> to bed... forever! :-) > > No. We’re not adding yet another up call. We’ve already got two... > I was thinking the call_usermodehelper() would replace the rpc_pipfs() upcall... but just remembered call_usermodehelper() does not have a clean way to pass data back into the kernel... darn! steved. -- 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
