• P
    locking/lockdep: Fix TRACE_IRQFLAGS vs. NMIs · ed004953
    peterz@infradead.org 提交于
    Prior to commit:
    
      859d069e ("lockdep: Prepare for NMI IRQ state tracking")
    
    IRQ state tracking was disabled in NMIs due to nmi_enter()
    doing lockdep_off() -- with the obvious requirement that NMI entry
    call nmi_enter() before trace_hardirqs_off().
    
    [ AFAICT, PowerPC and SH violate this order on their NMI entry ]
    
    However, that commit explicitly changed lockdep_hardirqs_*() to ignore
    lockdep_off() and breaks every architecture that has irq-tracing in
    it's NMI entry that hasn't been fixed up (x86 being the only fixed one
    at this point).
    
    The reason for this change is that by ignoring lockdep_off() we can:
    
      - get rid of 'current->lockdep_recursion' in lockdep_assert_irqs*()
        which was going to to give header-recursion issues with the
        seqlock rework.
    
      - allow these lockdep_assert_*() macros to function in NMI context.
    
    Restore the previous state of things and allow an architecture to
    opt-in to the NMI IRQ tracking support, however instead of relying on
    lockdep_off(), rely on in_nmi(), both are part of nmi_enter() and so
    over-all entry ordering doesn't need to change.
    Signed-off-by: NPeter Zijlstra (Intel) <peterz@infradead.org>
    Signed-off-by: NIngo Molnar <mingo@kernel.org>
    Link: https://lore.kernel.org/r/20200727124852.GK119549@hirez.programming.kicks-ass.net
    ed004953
Kconfig.debug 76.1 KB