From: Andrew Morton <akpm@linux-foundation.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: righiandr@users.sourceforge.net,
Bernd Eckenfels <ecki@lina.inka.de>,
linux-kernel@vger.kernel.org, Rik van Riel <riel@redhat.com>,
linux-mm@kvack.org
Subject: Re: [PATCH 1/2] limit print_fatal_signal() rate (was: [RFC] log out-of-virtual-memory events)
Date: Thu, 24 May 2007 09:23:36 -0700 [thread overview]
Message-ID: <20070524092336.b0b8cd8d.akpm@linux-foundation.org> (raw)
In-Reply-To: <20070524095503.GA14783@elte.hu>
On Thu, 24 May 2007 11:55:03 +0200 Ingo Molnar <mingo@elte.hu> wrote:
>
> * Andrew Morton <akpm@linux-foundation.org> wrote:
>
> > On Thu, 24 May 2007 09:58:35 +0200 Ingo Molnar <mingo@elte.hu> wrote:
> >
> > >
> > > * Andrew Morton <akpm@linux-foundation.org> 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.
next prev parent reply other threads:[~2007-05-24 16:24 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-17 16:24 [RFC] log out-of-virtual-memory events Andrea Righi
2007-05-17 18:22 ` Rik van Riel
2007-05-18 6:28 ` signals logged / " Jan Engelhardt
2007-05-18 11:47 ` Andi Kleen
2007-05-19 7:46 ` Jan Engelhardt
2007-05-19 9:35 ` Andrea Righi
2007-05-19 10:06 ` Jan Engelhardt
2007-05-19 10:16 ` Andrea Righi
2007-05-20 0:14 ` Folkert van Heusden
2007-05-20 3:55 ` Eric Dumazet
2007-05-20 11:21 ` Folkert van Heusden
2007-05-20 16:08 ` Stephen Hemminger
2007-05-20 16:12 ` Folkert van Heusden
2007-05-20 20:38 ` Jan Engelhardt
2007-05-20 20:55 ` Folkert van Heusden
2007-05-20 21:14 ` Andi Kleen
2007-05-20 21:20 ` Folkert van Heusden
2007-05-20 21:23 ` Folkert van Heusden
2007-05-20 22:24 ` Andi Kleen
2007-05-20 22:22 ` Jeff Dike
2007-05-21 11:26 ` Gábor Lénárt
2007-05-21 10:45 ` Andrea Righi
2007-05-21 11:04 ` Folkert van Heusden
2007-05-21 12:30 ` Jan Engelhardt
2007-05-21 12:47 ` Folkert van Heusden
2007-05-21 13:58 ` Andrea Righi
2007-05-21 18:59 ` Folkert van Heusden
2007-05-21 22:15 ` Andrea Righi
2007-05-23 18:00 ` Satyam Sharma
2007-05-23 18:45 ` Folkert van Heusden
2007-06-10 19:53 ` Folkert van Heusden
2007-06-10 20:06 ` Jiri Kosina
2007-06-10 20:37 ` Jan Engelhardt
2007-05-18 7:50 ` Andrea Righi
2007-05-18 9:16 ` Robin Holt
2007-05-18 15:55 ` Andrea Righi
2007-05-18 16:05 ` Andrea Righi
2007-05-18 16:34 ` Bernd Eckenfels
2007-05-19 10:33 ` [PATCH 1/2] limit print_fatal_signal() rate (was: [RFC] log out-of-virtual-memory events) Andrea Righi
2007-05-21 3:31 ` Andrew Morton
2007-05-21 10:44 ` [PATCH 1/2] limit print_fatal_signal() rate Andrea Righi
2007-05-24 7:58 ` [PATCH 1/2] limit print_fatal_signal() rate (was: [RFC] log out-of-virtual-memory events) Ingo Molnar
2007-05-24 8:15 ` Andrew Morton
2007-05-24 9:55 ` Ingo Molnar
2007-05-24 16:23 ` Andrew Morton [this message]
2007-05-24 8:50 ` [PATCH 1/2] limit print_fatal_signal() rate Andrea Righi
2007-05-24 9:58 ` Ingo Molnar
2007-05-24 9:57 ` [PATCH 1/2] limit print_fatal_signal() rate (was: [RFC] log out-of-virtual-memory events) Ingo Molnar
2007-05-18 16:36 ` [RFC] log out-of-virtual-memory events Bernd Eckenfels
2007-05-19 10:34 ` [PATCH 2/2] log out-of-virtual-memory events (was: [RFC] log out-of-virtual-memory events) Andrea Righi
2007-05-21 3:32 ` Andrew Morton
2007-05-21 10:48 ` [PATCH 2/2] log out-of-virtual-memory events Andrea Righi
2007-05-20 0:15 ` [RFC] " Folkert van Heusden
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=20070524092336.b0b8cd8d.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=ecki@lina.inka.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@elte.hu \
--cc=riel@redhat.com \
--cc=righiandr@users.sourceforge.net \
/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;
as well as URLs for NNTP newsgroup(s).