The patch titled
limit print_fatal_signal() rate
has been removed from the -mm tree. Its filename was
vdso-print-fatal-signals-fix.patch
This patch was dropped because it reduces the usefulness, and it's a root-opt-in thing anyway
------------------------------------------------------
Subject: limit print_fatal_signal() rate
From: Andrea Righi <righiandr@xxxxxxxxxxxxxxxxxxxxx>
Limit the rate of print_fatal_signal() to avoid potential denial-of-service
attacks.
Signed-off-by: Andrea Righi <a.righi@xxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
kernel/signal.c | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff -puN kernel/signal.c~vdso-print-fatal-signals-fix kernel/signal.c
--- a/kernel/signal.c~vdso-print-fatal-signals-fix
+++ a/kernel/signal.c
@@ -709,7 +709,10 @@ int print_fatal_signals = 0;
static void print_fatal_signal(struct pt_regs *regs, int signr)
{
- printk("%s/%d: potentially unexpected fatal signal %d.\n",
+ if (unlikely(!printk_ratelimit()))
+ return;
+
+ printk(KERN_WARNING "%s/%d: potentially unexpected fatal signal %d.\n",
current->comm, current->pid, signr);
#ifdef __i386__
_
Patches currently in -mm which might be from righiandr@xxxxxxxxxxxxxxxxxxxxx are
avr32-ratelimit-segfault-reporting-rate.patch
bug-in-i386-mtrr-initialization.patch
x86_64-ratelimit-segfault-reporting-rate.patch
vdso-print-fatal-signals-fix.patch
-
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
