• John Ogness's avatar
    printk: remove safe buffers · 93d102f0
    John Ogness authored
    With @logbuf_lock removed, the high level printk functions for
    storing messages are lockless. Messages can be stored from any
    context, so there is no need for the NMI and safe buffers anymore.
    Remove the NMI and safe buffers.
    
    Although the safe buffers are removed, the NMI and safe context
    tracking is still in place. In these contexts, store the message
    immediately but still use irq_work to defer the console printing.
    
    Since printk recursion tracking is in place, safe context tracking
    for most of printk is not needed. Remove it. Only safe context
    tracking relating to the console and console_owner locks is left
    in place. This is because the console and console_owner locks are
    needed for the actual printing.
    Signed-off-by: default avatarJohn Ogness <john.ogness@linutronix.de>
    Reviewed-by: default avatarPetr Mladek <pmladek@suse.com>
    Signed-off-by: default avatarPetr Mladek <pmladek@suse.com>
    Link: https://lore.kernel.org/r/20210715193359.25946-4-john.ogness@linutronix.de
    93d102f0
nmi_backtrace.c 3.16 KB