From: Borislav Petkov <bp@alien8.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "Steven Rostedt" <rostedt@goodmis.org>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Peter Zijlstra" <peterz@infradead.org>,
LKML <linux-kernel@vger.kernel.org>,
"Ingo Molnar" <mingo@kernel.org>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Subject: Re: [PATCH v2] printk: Add kernel parameter to disable writes to /dev/kmsg
Date: Tue, 26 Apr 2016 13:01:09 +0200 [thread overview]
Message-ID: <20160426110109.GD17845@pd.tnic> (raw)
In-Reply-To: <CA+55aFx0VWvoSxNDE34j4u2nq1QEOaicmTeYmVWRmesdBXLGeA@mail.gmail.com>
On Mon, Apr 25, 2016 at 01:23:36PM -0700, Linus Torvalds wrote:
> I really don't think this should be about open/close, but about rate
> limiting writes.
FWIW, I've taken your ratelimiting change into SLES at the time the
whole "fun" happened and we haven't had any complaints with it so far:
http://kernel.opensuse.org/cgit/kernel-source/commit/?id=bcda8bd37b684cfa63813c255594f32f5b268758
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
next prev parent reply other threads:[~2016-04-26 11:01 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-25 18:56 [PATCH v2] printk: Add kernel parameter to disable writes to /dev/kmsg Steven Rostedt
2016-04-25 19:06 ` Peter Zijlstra
2016-04-25 19:18 ` Greg Kroah-Hartman
2016-04-25 19:24 ` Peter Zijlstra
2016-04-25 19:44 ` Andrew Morton
2016-04-25 19:54 ` Greg Kroah-Hartman
2016-04-25 20:00 ` Steven Rostedt
2016-04-25 20:23 ` Linus Torvalds
2016-04-25 20:34 ` Steven Rostedt
2016-04-25 20:45 ` Linus Torvalds
2016-04-25 21:23 ` Steven Rostedt
2016-04-26 11:01 ` Borislav Petkov [this message]
2016-04-26 11:12 ` Peter Zijlstra
2016-04-25 19:30 ` Steven Rostedt
2016-04-25 19:28 ` Linus Torvalds
2016-04-25 19:34 ` Linus Torvalds
2016-04-25 19:35 ` Steven Rostedt
2016-04-25 19:44 ` Steven Rostedt
2016-04-26 5:36 ` Ingo Molnar
2016-04-26 10:43 ` Bjørn Mork
2016-04-26 11:09 ` Peter Zijlstra
2016-04-25 19:46 ` Andi Kleen
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=20160426110109.GD17845@pd.tnic \
--to=bp@alien8.de \
--cc=akpm@linux-foundation.org \
--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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.