Skip to content
  • Steven Rostedt (Red Hat)'s avatar
    ring-buffer: Give NMIs a chance to lock the reader_lock · 289a5a25
    Steven Rostedt (Red Hat) authored
    
    
    Currently, if an NMI does a dump of a ring buffer, it disables
    all ring buffers from ever doing any writes again. This is because
    it wont take the locks for the cpu_buffer and this can cause
    corruption if it preempted a read, or a read happens on another
    CPU for the current cpu buffer. This is a bit overkill.
    
    First, it should at least try to take the lock, and if it fails
    then disable it. Also, there's no need to disable all ring
    buffers, even those that are unrelated to what is being read.
    Only disable the per cpu ring buffer that is being read if
    it can not get the lock for it.
    
    Signed-off-by: default avatarSteven Rostedt <rostedt@goodmis.org>
    289a5a25