From: Jeff Layton <jlayton@redhat.com>
To: Steve French <smfrench@gmail.com>
Cc: Borislav Petkov <bp@alien8.de>,
LKML <linux-kernel@vger.kernel.org>,
Joe Perches <joe@perches.com>, Steve French <sfrench@samba.org>,
linux-cifs@vger.kernel.org
Subject: Re: [PATCH] cifs: Do not enable debugging code by default
Date: Tue, 18 Dec 2012 07:13:17 -0500 [thread overview]
Message-ID: <20121218071317.01cbc41b@tlielax.poochiereds.net> (raw)
In-Reply-To: <CAH2r5mt=4ZoGR_4hP52uHsZabXpPfh1sa1X0GSg6W4=fawNFnA@mail.gmail.com>
On Mon, 17 Dec 2012 09:30:33 -0600
Steve French <smfrench@gmail.com> wrote:
> 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@alien8.de> 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@perches.com>
> > Cc: Jeff Layton <jlayton@redhat.com>
> > Cc: Steve French <sfrench@samba.org>
> > Cc: linux-cifs@vger.kernel.org
> > Signed-off-by: Borislav Petkov <bp@alien8.de>
> > ---
> > 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
> >
I agree that we often need cifsFYI debug info in order to troubleshoot
problems. The question here though is whether compiling those in ought
to be the default.
In generic distro kernels, I think we do want that turned on even in
non-debug kernels. On an embedded arch, it's less compelling.
Might it make sense to couple this change with a change to the
CONFIG_CIFS_DEBUG help text? Something like:
"This option defaults to 'N', but enabling this is strongly encouraged
unless memory is severely constrained."
Then we can just try to make sure non-embedded distros enable it.
--
Jeff Layton <jlayton@redhat.com>
next prev parent reply other threads:[~2012-12-18 12:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-17 9:38 Borislav Petkov
2012-12-17 15:30 ` Steve French
2012-12-18 12:13 ` Jeff Layton [this message]
2012-12-18 14:44 ` Borislav Petkov
2012-12-18 15:07 ` Jeff Layton
2012-12-18 15:19 ` Borislav Petkov
2012-12-18 15:33 ` Steve French
2012-12-18 18:10 ` vfs trace points?: was: " Joe Perches
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20121218071317.01cbc41b@tlielax.poochiereds.net \
--to=jlayton@redhat.com \
--cc=bp@alien8.de \
--cc=joe@perches.com \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sfrench@samba.org \
--cc=smfrench@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®