I don't think taking out debugging makes sense - we need debugging a lot more often than expected even to diagnose user errors (usually relating to session establishment failures, since we are very limited in how much information can be passed back in mount). If we had dynamic trace points for cifs and for common vfs entry points, or if the distros shipped dual cifs modules (one with debugging and one without), I wouldn't mind disabling it - but multiple times a month we have to diagnose user problems (sometimes user errors, sometimes server bugs etc.) by enabling debugging. On Mon, Dec 17, 2012 at 3:38 AM, Borislav Petkov <bp@xxxxxxxxx> wrote: > Debugging code is generally disabled in the configurator since it is > only for devs and testers and not for the majority of the installations. > > Cc: Joe Perches <joe@xxxxxxxxxxx> > Cc: Jeff Layton <jlayton@xxxxxxxxxx> > Cc: Steve French <sfrench@xxxxxxxxx> > Cc: linux-cifs@xxxxxxxxxxxxxxx > Signed-off-by: Borislav Petkov <bp@xxxxxxxxx> > --- > fs/cifs/Kconfig | 1 - > 1 file changed, 1 deletion(-) > > diff --git a/fs/cifs/Kconfig b/fs/cifs/Kconfig > index 21ff76c22a17..241a0e2853c5 100644 > --- a/fs/cifs/Kconfig > +++ b/fs/cifs/Kconfig > @@ -124,7 +124,6 @@ config CIFS_ACL > > config CIFS_DEBUG > bool "Enable CIFS debugging routines" > - default y > depends on CIFS > help > Enabling this option adds helpful debugging messages to > -- > 1.8.1.rc2 > > -- > To unsubscribe from this list: send the line "unsubscribe linux-cifs" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html -- Thanks, Steve -- To unsubscribe from this list: send the line "unsubscribe linux-cifs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
