linux-kernel - Re: [PATCH v2] printk: Add kernel parameter to disable writes to /dev/kmsg

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 25 Apr 2016 15:44:05 -0400
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	Peter Zijlstra <peterz@...radead.org>,
	LKML <linux-kernel@...r.kernel.org>,
	Ingo Molnar <mingo@...nel.org>, Borislav Petkov <bp@...en8.de>,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Uwe Kleine-König 
	<u.kleine-koenig@...gutronix.de>
Subject: Re: [PATCH v2] printk: Add kernel parameter to disable writes to
 /dev/kmsg

On Mon, 25 Apr 2016 12:28:30 -0700
Linus Torvalds <torvalds@...ux-foundation.org> wrote:

> On Mon, Apr 25, 2016 at 12:06 PM, Peter Zijlstra <peterz@...radead.org> wrote:
> 
> I think it should be a tristate with "yes/no/ratelimit", and let's
> default to ratelimit.
> 

Also note that ratelimit wouldn't have solved my issue either. It
wasn't that systemd was rapidly spewing into the kernel buffers. It was
doing it gradually, for every connection that I made to the box (lots
of automated connections were also being logged). I believe something
happened on Friday but due to all the unnecessary logging over the
weekend, I lost it.

To make matters worse, I lost my /var/log/syslog data from then.
logrotate was a bit more destructive than I expected.

-- Steve