From: Jeff Layton <jlayton@redhat.com>
To: Borislav Petkov <bp@alien8.de>
Cc: Steve French <smfrench@gmail.com>,
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 10:07:02 -0500 [thread overview]
Message-ID: <20121218100702.478fc1b1@tlielax.poochiereds.net> (raw)
In-Reply-To: <20121218144452.GB31255@liondog.tnic>
On Tue, 18 Dec 2012 15:44:52 +0100
Borislav Petkov <bp@alien8.de> wrote:
> On Tue, Dec 18, 2012 at 07:13:17AM -0500, Jeff Layton wrote:
> > 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."
>
> ... or we make it default n if EMBEDDED, otherwise default y + changing
> the help text?
>
> > Then we can just try to make sure non-embedded distros enable it.
>
> Yeah, I don't think distros look at the help text... or?
>
Yeah, not many do, but presumably they'll set it once and forget about
it. Once someone straightens them out, they should rarely break.
OTOH, the value of defaulting to "N" is pretty low here. Maybe it would
just be best to just drop this patch and have the embedded folks turn
this off on their own.
--
Jeff Layton <jlayton@redhat.com>
next prev parent reply other threads:[~2012-12-18 15:07 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
2012-12-18 14:44 ` Borislav Petkov
2012-12-18 15:07 ` Jeff Layton [this message]
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=20121218100702.478fc1b1@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®