Date: Fri, 12 Apr 1996 15:57:22 -0400 (EDT) From: Sujal Patel <smpatel@umiacs.umd.edu> To: Poul-Henning Kamp <phk@critter.tfs.com> Cc: Paul Traina <pst@Shockwave.COM>, current@FreeBSD.org Subject: Re: log_in_vain stuff Message-ID: <Pine.NEB.3.92.960412155501.514V-100000@xi.dorm.umd.edu> In-Reply-To: <14797.829324640@critter.tfs.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 12 Apr 1996, Poul-Henning Kamp wrote: > > That sounds way too complicated. I think you should just leave them off, > > turn them on for debugging, and if you want them on, they do need internal > > rate limiting in the kernel (a simple check should be sufficient). > > We have something very similar a couple of other places, stray ints for > instance... Yes but since stray interrupts cause the exact same log message, syslog will compact that down to: /kernel: stray irq 7 last message repeated 7199 times Besides, there really isn't a way for a remote attacker to cause a stray irq. Sujal
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.NEB.3.92.960412155501.514V-100000>