On May 3, 2013, at 3:39 PM, Jeff Layton <jlayton@xxxxxxxxxx> wrote: > On Fri, 3 May 2013 15:26:09 -0400 > Chuck Lever <chuck.lever@xxxxxxxxxx> wrote: > >> I don't expect this issue to last for release after release. A moment ago you agreed that this shouldn't be intractable, so I fail to see the need to start wiring up long-term workarounds. >> >> Can't we just agree on a fix, and then get that into 3.10 as a regression fix? >> > > I'm happy to help...I'm just not sure what you're proposing as the fix > for the problem. What are you suggesting we do? The kernel has historically had difficulty determining the status of GSS support in user space. One way to remedy this would be to have "systemctl disable nfs-server.service" blacklist the kernel's GSS module, and "systemctl enable nfs-server.service" remove the blacklisting. This mechanism would have to be sensitive to both gssd and svcgssd, of course. -- 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
