Re: [PATCH 1/2] limit print_fatal_signal() rate

From: Andrea Righi
Date: Thu May 24 2007 - 04:51:19 EST


Ingo Molnar wrote:
> * Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> 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 from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/