From: "J. Bruce Fields" <bfields@fieldses.org>
To: Peter Staubach <staubach@redhat.com>
Cc: Valdis.Kletnieks@vt.edu,
"Dr. David Alan Gilbert" <linux@treblig.org>,
Randy Dunlap <randy.dunlap@oracle.com>,
neilb@suse.de, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Add source address to sunrpc svc errors
Date: Wed, 29 Aug 2007 09:50:58 -0400 [thread overview]
Message-ID: <20070829135058.GA13803@fieldses.org> (raw)
In-Reply-To: <46D5767C.9050206@redhat.com>
On Wed, Aug 29, 2007 at 09:37:00AM -0400, Peter Staubach wrote:
> There are a lot of ways to discover who is throwing trash
> at your system other than the kernel printing messages.
>
> Tools such as tcpdump and tethereal/wireshark make much better
> tools for this purpose.
The use of printk's and dprintk's in the rpc and nfsd code seems a
little arbitrary in places. It would be worth grepping for them all,
figuring out how they're currently used, thinking about what we need
them for (to help administrators identify problems? to help testers
provide debugging information to developers?), and how they might be
abused (remote hosts and unprivileged local users shouldn't be able to
spam the logs), developing some uniform policies, and submitting
patches.
I'm not volunteering, but if someone's interested I think it could be
really helpful, especially if it helps increase the usefulness of bug
reports.
--b.
next prev parent reply other threads:[~2007-08-29 13:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-25 1:26 [PATCH] Add source address to sunrpc svc errors Dr. David Alan Gilbert
2007-08-25 1:56 ` Randy Dunlap
2007-08-25 15:09 ` Dr. David Alan Gilbert
2007-08-27 21:43 ` J. Bruce Fields
2007-08-28 18:03 ` Dr. David Alan Gilbert
2007-08-28 18:56 ` J. Bruce Fields
2007-09-01 19:27 ` Dr. David Alan Gilbert
2007-08-28 19:12 ` Valdis.Kletnieks
2007-08-28 19:19 ` J. Bruce Fields
2007-08-29 18:26 ` Valdis.Kletnieks
2007-08-29 13:37 ` Peter Staubach
2007-08-29 13:50 ` J. Bruce Fields [this message]
2007-08-29 19:41 ` Valdis.Kletnieks
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=20070829135058.GA13803@fieldses.org \
--to=bfields@fieldses.org \
--cc=Valdis.Kletnieks@vt.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@treblig.org \
--cc=neilb@suse.de \
--cc=randy.dunlap@oracle.com \
--cc=staubach@redhat.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