On Thu, Feb 07, 2013 at 12:12:24PM -0500, Chuck Lever wrote: > > On Feb 7, 2013, at 12:03 PM, Chuck Lever <chuck.lever@xxxxxxxxxx> wrote: > > I've thought a little about that. There is already a logged warning if a gssd upcall times out. But it's hard to tell inside the kernel why a module doesn't load. These all look pretty much the same to the RPC layer: > > > > - module is blacklisted or not installed? > > - GSS support wasn't built? > > - filesystem corruption? > > - export specifies a security flavor the RPC client doesn't recognize? > > > > I suppose I could add something here, but I wonder about the false alarms. > > How about this: > > "Warning: export specifies a security flavor that isn't supported" Sounds fine. With a guard so we just say it once. Bonus if we could say which export or which flavor? --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
