From: Valdis.Kletnieks@vt.edu
To: Peter Staubach <staubach@redhat.com>
Cc: "J. Bruce Fields" <bfields@fieldses.org>,
"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 15:41:58 -0400 [thread overview]
Message-ID: <13825.1188416518@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Wed, 29 Aug 2007 09:37:00 EDT." <46D5767C.9050206@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 776 bytes --]
On Wed, 29 Aug 2007 09:37:00 EDT, Peter Staubach said:
> 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.
Given the number of times I've had to use tcpdump and wireshark to wade
through literally gigabyte traces looking for stuff specifically because
the kernel *didn't* printk information it had handy, I'm not too sympathetic.
Especially when the printk in question is currently saying "I know who's
causing the problem but I'm not going to tell you, nyah nyah"....
(And if there's better ways than kernel printing messages, does that mean we
should deprecate the iptables '-j LOG' target while we're at it?)
[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]
prev parent reply other threads:[~2007-08-29 19:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-25 1:26 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
2007-08-29 19:41 ` Valdis.Kletnieks [this message]
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=13825.1188416518@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=bfields@fieldses.org \
--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
all inboxes | Powered by JetHome®