diff options
| author | John Ogness <john.ogness@linutronix.de> | 2021-07-15 21:39:56 +0206 |
|---|---|---|
| committer | Petr Mladek <pmladek@suse.com> | 2021-07-26 15:09:34 +0200 |
| commit | 93d102f094be9beab28e5afb656c188b16a3793b (patch) | |
| tree | bc1a38f9ecdabf5e262e433633c68ec6568032ef /lib | |
| parent | 002eb6ad075142e5940122c7fcee71cf1e906e29 (diff) | |
| download | linux-93d102f094be9beab28e5afb656c188b16a3793b.tar.gz linux-93d102f094be9beab28e5afb656c188b16a3793b.tar.xz | |
printk: remove safe buffers
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: John Ogness <john.ogness@linutronix.de>
Reviewed-by: Petr Mladek <pmladek@suse.com>
Signed-off-by: Petr Mladek <pmladek@suse.com>
Link: https://lore.kernel.org/r/20210715193359.25946-4-john.ogness@linutronix.de
Diffstat (limited to 'lib')
| -rw-r--r-- | lib/nmi_backtrace.c | 6 |
1 files changed, 0 insertions, 6 deletions
diff --git a/lib/nmi_backtrace.c b/lib/nmi_backtrace.c index dae233c5f597..9813a983d024 100644 --- a/lib/nmi_backtrace.c +++ b/lib/nmi_backtrace.c @@ -75,12 +75,6 @@ void nmi_trigger_cpumask_backtrace(const cpumask_t *mask, touch_softlockup_watchdog(); } - /* - * Force flush any remote buffers that might be stuck in IRQ context - * and therefore could not run their irq_work. - */ - printk_safe_flush(); - clear_bit_unlock(0, &backtrace_flag); put_cpu(); } |