lkml.org 
[lkml]   [2011]   [Dec]   [21]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: [RFC][PATCH 0/7] improve printk reliability
From
Date
On Wed, 2011-12-21 at 11:57 +0100, Peter Zijlstra wrote:
> Hi,
>
> So these are my current efforts to make my own console output more
> reliable. I've hit every deadlock described in this series and a few
> more.
>
> With these patches applied I can printk() and WARN() from inside
> scheduler context and not have my machine deadlock, even without the
> aid of early_printk().
>
> While I'll go an remove the sole printk() I found in the scheduler
> so that we don't have to rely on the console doing this, it is good
> to have a reliable console that can do this.
>
> As it stands some of the patches, the semaphore one in particular,
> are really too ugly to live so I won't push those but wanted to share
> anyway.
>
> Debugging this was 'fun', and I really hope to not have to do it
> again :-)

Also, these patches enable lockdep over printk(), allowing lockdep to
detect previously undetected deadlocks with console implementations,
irrespective of rq->lock.




\
 
 \ /
  Last update: 2011-12-21 12:25    [W:0.106 / U:0.788 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site