Messages in this thread | | | Date | Wed, 19 Dec 2018 10:46:57 +0900 | From | Sergey Senozhatsky <> | Subject | Re: [RFC][PATCH] printk: increase devkmsg write() ratelimit |
| |
On (12/18/18 18:47), Borislav Petkov wrote: > So how much is not strict? > > And what happens if you raise that ratelimiting level and the *one* line > which is most important for debugging an issue
Like you said, for debugging devkmsg=off works just fine. I don't mind the ratelimiting and want to keep it; I just don't want errors to be ratelimited.
> All I'm saying is, gradually raising the limit is the wrong approach > - there will always be a case where something important doesn't get > logged.
Well, OK.
> What we need is a different solution, maybe what Rostedt proposes or > so...
Sure, a different approach and idea are welcome. This is RFC thread.
-ss
| |