On Wed, Feb 17, 2016 at 11:40:49AM +0100, Peter Zijlstra wrote: > Mucking with the semaphore implementation just because printk() is > terminally broken shite really doesn't fly.
Jan is currently working on the terminally broken shite, and I expect it makes printk() robuster. I just tried this patch because I though the semaphore also need to be fixed and furthermore it can fix a deadlock by removing the waiting within trylock. I think it's reasonable. Wrong?
