Re: [PATCH -v4 2/2] printk: Add kernel parameter to control writes to /dev/kmsg
From: Borislav Petkov
Date: Mon Jul 18 2016 - 05:06:33 EST
On Mon, Jul 18, 2016 at 04:17:12PM +0800, Dave Young wrote:
> Because IMHO it is wrong, they can not be ratelimited because the writing could
> be from different userspace programs.
It is ratelimited by interface openers.
> Simply ratelimiting different sources of writing is pointless to me.
So what are you arguing for? What is the *actual* *real-life* *use* case
you think will be handicapped?
> One can only see messages they would like to see by luck, it is worse
> than off.
THAT'S WHY YOU BOOT WITH "printk.devkmsg=on" TO SEE THEM ALL!
The /dev/kmsg thing was added for the more or less, wrong, historic
reasons and userspace started abusing it and interfering with kernel
operation. That's why we're adding this tristate option.
In the default case we're ratelimiting writes to it because they should
not interfere with kernel operation.
[ Frankly, those writes are pretty much useless to the normal user so
we can just as well ignore them but WTH. ]
So give me a concrete problem you see with the ralimiting and not some
notion of a feeling you might have of it being pointless, ok?
ECO tip #101: Trim your mails when you reply.