[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160719064959.GA25563@nazgul.tnic>
Date: Tue, 19 Jul 2016 08:49:59 +0200
From: Borislav Petkov <bp@...en8.de>
To: Dave Young <dyoung@...hat.com>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
LKML <linux-kernel@...r.kernel.org>, Franck Bui <fbui@...e.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Ingo Molnar <mingo@...nel.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Peter Zijlstra <peterz@...radead.org>,
Steven Rostedt <rostedt@...dmis.org>,
Uwe Kleine-König
<u.kleine-koenig@...gutronix.de>
Subject: Re: [PATCH -v4 2/2] printk: Add kernel parameter to control writes
to /dev/kmsg
On Tue, Jul 19, 2016 at 08:35:07AM +0800, Dave Young wrote:
> Ok, for example below (A and B can be any program, systemd or other logging
> utility, dracut scripts...)
Are you even reading what I'm writing to you?
I asked for real-life use case and I told you the ratelimiting is done
by openers of /dev/kmsg.
> Program A:
> for (i = 0; i < 100; i++)
> write an error message A1
Because this is a real use case, right? Write A1 100 times in a loop?!
You gotta be f*cking kidding me!
Now I'm going to ignore you know until you start reading what I'm
writing to you.
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
--
Powered by blists - more mailing lists