Re: printk considered harmful (was: [TECH TOPIC] asynchronous printk)

2016-11-04 Thread Sergey Senozhatsky
Hi Jan, On (11/04/16 00:28), Jan Kara wrote: [..] > > I'm still not entirely sure if I want to split async pintk and printk > > deadlock rework. these things want to come together, for a number of > > reasons. or, at least, push the async printk before printk deadlock > > rework. > > Yep, please

Re: printk considered harmful (was: [TECH TOPIC] asynchronous printk)

2016-11-03 Thread Jan Kara
On Fri 04-11-16 03:01:31, Sergey Senozhatsky wrote: > fix a typo > > On (11/04/16 02:31), Sergey Senozhatsky wrote: > [..] > > #4 console semaphore > > discussion outcome: > > we agreed that we can do better here and that it makes sense to do > IOW, console

Re: printk considered harmful (was: [TECH TOPIC] asynchronous printk)

2016-11-03 Thread Sergey Senozhatsky
fix a typo On (11/04/16 02:31), Sergey Senozhatsky wrote: [..] > #4 console semaphore > discussion outcome: > we agreed that we can do better here and that it makes sense to do IOW, console semaphore thing can be improv

Re: printk considered harmful (was: [TECH TOPIC] asynchronous printk)

2016-11-03 Thread Sergey Senozhatsky
[Cc linux-kernel] Hello, On (11/02/16 10:06), Joe Perches wrote: > Hello all. > > Can you please post notes for whatever is proposed here somewhere? we covered 4 topics: #1 deadlocks and recursion in printk discussion outcome: I published an updated printk_safe patch last week (addresses re