[lkml]   [2007]   [May]   [24]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH 1/2] limit print_fatal_signal() rate
Ingo Molnar wrote:
> * Andrew Morton <> 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:

@@ -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

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2007-05-24 10:55    [W:0.125 / U:0.504 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site