[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87fsp9pm6q.fsf@jogness.linutronix.de>
Date: Thu, 27 Jan 2022 10:28:53 +0106
From: John Ogness <john.ogness@...utronix.de>
To: Stephen Brennan <stephen.s.brennan@...cle.com>,
Sergey Senozhatsky <senozhatsky@...omium.org>,
Petr Mladek <pmladek@...e.com>
Cc: Arnd Bergmann <arnd@...db.de>,
Steven Rostedt <rostedt@...dmis.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Stephen Brennan <stephen.s.brennan@...cle.com>,
Sebastian Reichel <sre@...nel.org>,
Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
Luis Chamberlain <mcgrof@...nel.org>,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 4/4] printk: Drop console_sem during panic
On 2022-01-26, Stephen Brennan <stephen.s.brennan@...cle.com> wrote:
> --- a/kernel/printk/printk.c
> +++ b/kernel/printk/printk.c
> @@ -2759,7 +2782,7 @@ void console_unlock(void)
> * flush, no worries.
> */
> retry = prb_read_valid(prb, next_seq, NULL);
> - if (retry && console_trylock())
> + if (retry && !abandon_console_lock_in_panic() && console_trylock())
As Sergey suggested [0], I would like to see the call to
abandon_console_lock_in_panic() move inside console_trylock(). This will
help to avoid the race between NMI CPU halt and the internal sema.lock
spinlock.
John Ogness
[0] https://lore.kernel.org/all/YfJFjHdg%2FkhNXiRd@google.com
Powered by blists - more mailing lists