| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Wed, 29 Aug 2007 09:50:58 -0400 From: "J. Bruce Fields" <bfields@...ldses.org> To: Peter Staubach <staubach@...hat.com> Cc: Valdis.Kletnieks@...edu, "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 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. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists