• S
    ring-buffer: do not disable ring buffer on oops_in_progress · 464e85eb
    Steven Rostedt 提交于
    The commit:
    
      commit e0fdace1
      Author: David Miller <davem@davemloft.net>
      Date:   Fri Aug 1 01:11:22 2008 -0700
    
        debug_locks: set oops_in_progress if we will log messages.
    
        Otherwise lock debugging messages on runqueue locks can deadlock the
        system due to the wakeups performed by printk().
    Signed-off-by: NDavid S. Miller <davem@davemloft.net>
    Signed-off-by: NIngo Molnar <mingo@elte.hu>
    
    Will permanently set oops_in_progress on any lockdep failure.
    When this triggers it will cause any read from the ring buffer to
    permanently disable the ring buffer (not to mention no locking of
    printk).
    
    This patch removes the check. It keeps the print in NMI which makes
    sense. This is probably OK, since the ring buffer should not cause
    something to set oops_in_progress anyway.
    Signed-off-by: NSteven Rostedt <rostedt@goodmis.org>
    464e85eb
ring_buffer.c 79.0 KB