From: Borislav Petkov <bp@alien8.de> To: Andrew Morton <akpm@linux-foundation.org> Cc: LKML <linux-kernel@vger.kernel.org>, "Borislav Petkov" <bp@suse.de>, "Dave Young" <dyoung@redhat.com>, "Franck Bui" <fbui@suse.com>, "Greg Kroah-Hartman" <gregkh@linuxfoundation.org>, "Ingo Molnar" <mingo@kernel.org>, "Linus Torvalds" <torvalds@linux-foundation.org>, "Peter Zijlstra" <peterz@infradead.org>, "Steven Rostedt" <rostedt@goodmis.org>, "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de> Subject: [PATCH -v5 0/2] printk.devkmsg: Ratelimit it by default Date: Sat, 16 Jul 2016 08:17:43 +0200 Message-ID: <20160716061745.15795-1-bp@alien8.de> (raw) From: Borislav Petkov <bp@suse.de> Hi guys, here's v5 with Andrew's review comments addressed (I hope all). I've unified the setting names for both sysctl(2) and the kernel cmdline to "on", "off" and "ratelimit" so that there's no confusion anymore as to which sysctl number corresponds to what string. This should make dealing with that option straight-forward. Also, requested textual expansion regarding the reasoning for the current design has been added in comments and commit messages. Thanks. Changelog: ---------- v4: sorry for spamming so quickly again and not waiting for a week before resubmitting but I believe the stuff is ready for 4.8. So here's v4 with all the minor review comments addressed. v3: here's v3 integrating Ingo's comments. The thing is called printk.devkmsg= or printk_devkmsg now, depending on cmdline option or sysctl. v2: here's v2 with the requested sysctl option kernel.printk_kmsg and locking of the setting when printk.kmsg= is supplied on the command line. Patch 1 is unchanged. Patch 2 has grown the sysctl addition. v1: 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? Please queue, 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 | 7 ++ Documentation/sysctl/kernel.txt | 14 ++++ include/linux/printk.h | 9 +++ include/linux/ratelimit.h | 38 ++++++++-- kernel/printk/printk.c | 143 ++++++++++++++++++++++++++++++++++-- kernel/sysctl.c | 7 ++ lib/ratelimit.c | 10 ++- 7 files changed, 211 insertions(+), 17 deletions(-) -- 2.8.4
next reply index Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2016-07-16 6:17 Borislav Petkov [this message] 2016-07-16 6:17 ` [PATCH -v5 1/2] ratelimit: Extend to print suppressed messages on release Borislav Petkov 2016-07-16 6:17 ` [PATCH -v5 2/2] printk: Add kernel parameter to control writes to /dev/kmsg Borislav Petkov
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=20160716061745.15795-1-bp@alien8.de \ --to=bp@alien8.de \ --cc=akpm@linux-foundation.org \ --cc=bp@suse.de \ --cc=dyoung@redhat.com \ --cc=fbui@suse.com \ --cc=gregkh@linuxfoundation.org \ --cc=linux-kernel@vger.kernel.org \ --cc=mingo@kernel.org \ --cc=peterz@infradead.org \ --cc=rostedt@goodmis.org \ --cc=torvalds@linux-foundation.org \ --cc=u.kleine-koenig@pengutronix.de \ /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
LKML Archive on lore.kernel.org Archives are clonable: git clone --mirror https://lore.kernel.org/lkml/0 lkml/git/0.git git clone --mirror https://lore.kernel.org/lkml/1 lkml/git/1.git git clone --mirror https://lore.kernel.org/lkml/2 lkml/git/2.git git clone --mirror https://lore.kernel.org/lkml/3 lkml/git/3.git git clone --mirror https://lore.kernel.org/lkml/4 lkml/git/4.git git clone --mirror https://lore.kernel.org/lkml/5 lkml/git/5.git git clone --mirror https://lore.kernel.org/lkml/6 lkml/git/6.git git clone --mirror https://lore.kernel.org/lkml/7 lkml/git/7.git git clone --mirror https://lore.kernel.org/lkml/8 lkml/git/8.git git clone --mirror https://lore.kernel.org/lkml/9 lkml/git/9.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 lkml lkml/ https://lore.kernel.org/lkml \ linux-kernel@vger.kernel.org public-inbox-index lkml Example config snippet for mirrors Newsgroup available over NNTP: nntp://nntp.lore.kernel.org/org.kernel.vger.linux-kernel AGPL code for this site: git clone https://public-inbox.org/public-inbox.git