On Nov 12, 2013, at 11:56 AM, "Myklebust, Trond" <Trond.Myklebust@xxxxxxxxxx> wrote: > On Tue, 2013-11-12 at 11:15 -0500, Chuck Lever wrote: >> On Nov 12, 2013, at 11:08 AM, Jeff Layton <jlayton@xxxxxxxxxx> wrote: >> >>> On Tue, 12 Nov 2013 11:02:42 -0500 >>> Chuck Lever <chuck.lever@xxxxxxxxxx> wrote: >>> >>>> >>>> On Nov 12, 2013, at 8:00 AM, Jeff Layton <jlayton@xxxxxxxxxx> wrote: >>>> >>> What's the module loading solution? >> >> Load auth_rpcgss.ko only when rpc.gssd has been started. See the "[PATCH] Adding the nfs4_secure_mounts bool" thread... If auth_rpcgss.ko is not loaded, the kernel won't ever try to do an upcall. >> >> Then, systemd can be used to restart rpc.gssd if it crashes, maybe? Just a thought. > > You can trivially defeat that by compiling the gss code into the kernel. My solution is a workaround. It works for distributions that do not compile auth_rpcgss into the kernel, since they are the ones who provide an appropriate init script architecture. But it does not require a kernel code change, and it applies to every distribution I'm aware of. Since distributions typically do not use built-in GSS support, I'm not too concerned about whoever might be left over. And I never said that we shouldn't continue to mitigate the upcall timeout. Note that Jeff's solution didn't entirely eliminate the problem either. With either or both of these solutions in place, we are better off than we were before. -- 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
