[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6938.1188411973@turing-police.cc.vt.edu>
Date: Wed, 29 Aug 2007 14:26:13 -0400
From: Valdis.Kletnieks@...edu
To: "J. Bruce Fields" <bfields@...ldses.org>
Cc: "Dr. David Alan Gilbert" <linux@...blig.org>,
Randy Dunlap <randy.dunlap@...cle.com>, neilb@...e.de,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Add source address to sunrpc svc errors
On Tue, 28 Aug 2007 15:19:07 EDT, "J. Bruce Fields" said:
> On Tue, Aug 28, 2007 at 03:12:26PM -0400, Valdis.Kletnieks@...edu wrote:
> > On Mon, 27 Aug 2007 17:43:33 EDT, "J. Bruce Fields" said:
> > > I also wonder whether these shouldn't all be dprintk's instead of
> > > printk's. One misbehaving client could create a lot of noise in the
> > > logs.
> >
> > I shouldn't have to rebuild my kernel with debugging enabled just to see
> > who is throwing trash at my machine.
>
> Fair enough.
>
> The dprintk's throughout the nfs and sunrpc server and client code can
> be selectively enabled at runtime using a set of sysctls in
> sys/sunrpc/*_debug; see
>
> include/linux/lockd/debug.h
> include/linux/nfsd/debug.h
I looked at nfsd/debug.h, and saw the NFSD_DEBUG usage, and thought "Wow, if I
built it without RPC_DEBUG, I'm screwed". I didn't see where RPC_DEBUG was
enabled if CONFIG_SYSCTL was defined - having "compile in debugging code"
equated to "system has sysctl support" was as unexpected as the guy today who
didn't realize you needed SCSI support for an IDE CD/ROM. ;)
"You are trapped in a twisty maze of little #ifdef's, all different"... ;)
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists