From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752293AbcFNKMN (ORCPT ); Tue, 14 Jun 2016 06:12:13 -0400 Received: from mail.skyhub.de ([78.46.96.112]:56105 "EHLO mail.skyhub.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752203AbcFNKML (ORCPT ); Tue, 14 Jun 2016 06:12:11 -0400 From: Borislav Petkov To: Linus Torvalds , Steven Rostedt Cc: Greg Kroah-Hartman , Ingo Molnar , Peter Zijlstra , Andrew Morton , =?UTF-8?q?Uwe=20Kleine-K=C3=B6nig?= , LKML Subject: [PATCH 0/2] printk.kmsg: Ratelimit it by default Date: Tue, 14 Jun 2016 12:12:06 +0200 Message-Id: <1465899128-4522-1-git-send-email-bp@alien8.de> X-Mailer: git-send-email 2.7.3 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Borislav Petkov Ok, so how about these two? Rostedt is busy so I took Linus' old patch and Steven's last v2 and split and extended them with the comments people had on the last thread: https://lkml.kernel.org/r/20160425145606.598329f2@gandalf.local.home I hope, at least. So it is ratelimiting by default, with "on" and "off" cmdline options. I called the option somewhat a bit shorter too: "printk.kmsg" The current use cases of this and of which I'm aware are: * debug the kernel and thus shut up all interfering input from userspace, i.e. boot with "printk.kmsg=off" * debug userspace (and by that I mean systemd) by booting with "printk.kmsg=on" so that the ratelimiting is disabled and the kernel log gets all the spew. Thoughts? Thanks. Borislav Petkov (2): ratelimit: Extend to print suppressed messages on release printk: Add kernel parameter to control writes to /dev/kmsg Documentation/kernel-parameters.txt | 6 ++++ include/linux/ratelimit.h | 36 +++++++++++++++++++---- kernel/printk/printk.c | 57 +++++++++++++++++++++++++++++++------ lib/ratelimit.c | 6 ++-- 4 files changed, 90 insertions(+), 15 deletions(-) -- 2.7.3