On 02/09/2016 04:50 PM, Steven Rostedt wrote: > One thing is to find the spamming code and fix that.
We can't rely that there won't be never-ending concurrent printks, right? For one, in many setups user can cause printk flood. I think we must ensure that printk does not livelock.
