From: Andrea Righi <righiandr@users.sourceforge.net>
To: Ingo Molnar <mingo@elte.hu>
Cc: Andrew Morton <akpm@linux-foundation.org>,
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
Date: Thu, 24 May 2007 10:50:49 +0200 (MEST) [thread overview]
Message-ID: <465551DC.4060603@users.sourceforge.net> (raw)
In-Reply-To: <20070524075835.GC21138@elte.hu>
Ingo Molnar wrote:
> * Andrew Morton <akpm@linux-foundation.org> wrote:
>
>> Well OK. But vdso-print-fatal-signals.patch is designated
>> not-for-mainline anyway.
>
> btw., why? It's very, very useful to distro, early-boot-userspace and
> glibc development. The only add-on change should be to not print SIGKILL
> events. Otherwise it's very much a keeper. Hm?
>
Actually it seems that SIGKILLs are not printed. In get_signal_to_deliver() we have:
[snip]
@@ -1843,6 +1879,8 @@ relock:
* Anything else is fatal, maybe with a core dump.
*/
current->flags |= PF_SIGNALED;
+ if ((signr != SIGKILL) && print_fatal_signals)
+ print_fatal_signal(regs, signr);
if (sig_kernel_coredump(signr)) {
/*
* If it was able to dump core, this kills all
[snip]
-Andrea
--
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: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2007-05-24 8:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1Hp5PV-0001Bn-00@calista.eckenfels.net>
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
2007-05-24 8:50 ` Andrea Righi [this message]
2007-05-24 9:58 ` [PATCH 1/2] limit print_fatal_signal() rate 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
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=465551DC.4060603@users.sourceforge.net \
--to=righiandr@users.sourceforge.net \
--cc=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 \
/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