From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Thu, 24 May 2007 09:23:36 -0700 From: Andrew Morton Subject: Re: [PATCH 1/2] limit print_fatal_signal() rate (was: [RFC] log out-of-virtual-memory events) Message-Id: <20070524092336.b0b8cd8d.akpm@linux-foundation.org> In-Reply-To: <20070524095503.GA14783@elte.hu> References: <464ED258.2010903@users.sourceforge.net> <20070520203123.5cde3224.akpm@linux-foundation.org> <20070524075835.GC21138@elte.hu> <20070524011551.3d72a6e8.akpm@linux-foundation.org> <20070524095503.GA14783@elte.hu> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-linux-mm@kvack.org Return-Path: To: Ingo Molnar Cc: righiandr@users.sourceforge.net, Bernd Eckenfels , linux-kernel@vger.kernel.org, Rik van Riel , linux-mm@kvack.org List-ID: On Thu, 24 May 2007 11:55:03 +0200 Ingo Molnar wrote: > > * Andrew Morton wrote: > > > On Thu, 24 May 2007 09:58:35 +0200 Ingo Molnar wrote: > > > > > > > > * Andrew Morton wrote: > > > > > > > Well OK. But vdso-print-fatal-signals.patch is designated > > > > not-for-mainline anyway. > > > > > > btw., why? > > > > err, because that's what I decided a year ago. I wonder why ;) > > > > Perhaps because of the DoS thing, but it has a /proc knob and defaults > > to off, so it should be OK. > > yeah. There's also a boot option. To address the DoS angle, should i > make it optionally printk_ratelimit() perhaps? (although often the > messages come in streams and skipping a message can be annoying) I don't think so, really. It takes a deliberate act to turn the thing on, after all. I we _were_ concerned about the logspam then it might be better to make the feature turn itself off after 100 messages, rather than ratelimiting it. -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org