Re: [PATCH -v4 2/2] printk: Add kernel parameter to control writes to /dev/kmsg

[Dave Young <dyoung@redhat.com>]

On 07/19/16 at 08:49am, Borislav Petkov wrote:
> 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!

It is just emulating a use case, in a real life use case of course it shouldn't
be a for loop. Suppose checking a device existance every some period, it
is possible for same error messages being printed again and again, may for
same device, may for different device, but it is from same source code
line. I suppose you can understand, but you did not.

Please stop being angry, I was trying to understand you. I hope you can
also think from different point of view.

> 
> Now I'm going to ignore you know until you start reading what I'm
> writing to you.

Same to me, I will stop reply because I have tried my best but I'm
beginning have same feeling as you that is you just do not want to read
what I wrote, sigh.

Thanks
Dave