From: Rik van Riel <riel@surriel.com>
To: John Ogness <john.ogness@linutronix.de>,
Andrew Morton <akpm@linux-foundation.org>
Cc: Omar Sandoval <osandov@meta.com>,
linux-kernel@vger.kernel.org, Petr Mladek <pmladek@suse.com>,
Steven Rostedt <rostedt@goodmis.org>,
Sergey Senozhatsky <senozhatsky@chromium.org>,
kernel-team <kernel-team@meta.com>
Subject: Re: [RFC PATCH] nmi,printk: fix ABBA deadlock between nmi_backtrace and dump_stack_lvl
Date: Wed, 17 Jul 2024 09:47:48 -0400 [thread overview]
Message-ID: <93155b2ccafa43ed4845ae450451c6b8e27509cc.camel@surriel.com> (raw)
In-Reply-To: <87plrcqyii.fsf@jogness.linutronix.de>
On Wed, 2024-07-17 at 09:22 +0206, John Ogness wrote:
>
> The purpose of printk_cpu_sync_get_irqsave() is to avoid having the
> different backtraces being interleaved in the _ringbuffer_. It really
> isn't necessary that they are printed in that context. And indeed,
> there
> is no guarantee that they will be printed in that context anyway.
>
> Perhaps a simple solution would be for printk_cpu_sync_get_irqsave()
> to
> call printk_deferred_enter/_exit. Something like the below patch.
>
I think that would do the trick. The nmi_backtrace() printk is already
deferred, because of the check for in_nmi() in vprintk(), and this
change would put all the other users of printk_cpu_sync_get_irqsave()
on the exact same footing as nmi_backtrace().
Combing through the code a little, it looks like that would remove
the potential for this deadlock to happen again.
>
>
> diff --git a/include/linux/printk.h b/include/linux/printk.h
> index 65c5184470f1..1a6f5aac28bf 100644
> --- a/include/linux/printk.h
> +++ b/include/linux/printk.h
> @@ -315,8 +315,10 @@ extern void __printk_cpu_sync_put(void);
> #define printk_cpu_sync_get_irqsave(flags) \
> for (;;) { \
> local_irq_save(flags); \
> + printk_deferred_enter(); \
> if (__printk_cpu_sync_try_get()) \
> break; \
> + printk_deferred_exit(); \
> local_irq_restore(flags); \
> __printk_cpu_sync_wait(); \
> }
> @@ -329,6 +331,7 @@ extern void __printk_cpu_sync_put(void);
> #define printk_cpu_sync_put_irqrestore(flags) \
> do { \
> __printk_cpu_sync_put(); \
> + printk_deferred_exit(); \
> local_irq_restore(flags); \
> } while (0)
>
>
--
All Rights Reversed.
next prev parent reply other threads:[~2024-07-17 13:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-16 3:20 Rik van Riel
2024-07-17 7:16 ` John Ogness
2024-07-17 13:47 ` Rik van Riel [this message]
2024-07-18 7:25 ` John Ogness
2024-07-18 13:38 ` Rik van Riel
2024-07-18 14:09 ` John Ogness
2024-07-18 15:23 ` Rik van Riel
2024-07-24 12:56 ` Petr Mladek
2024-07-24 14:45 ` John Ogness
2024-07-24 15:08 ` Petr Mladek
2024-09-13 17:25 ` Rik van Riel
2024-09-16 14:33 ` Petr Mladek
2024-07-24 16:55 ` Rik van Riel
2024-07-24 12:45 ` Petr Mladek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=93155b2ccafa43ed4845ae450451c6b8e27509cc.camel@surriel.com \
--to=riel@surriel.com \
--cc=akpm@linux-foundation.org \
--cc=john.ogness@linutronix.de \
--cc=kernel-team@meta.com \
--cc=linux-kernel@vger.kernel.org \
--cc=osandov@meta.com \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=senozhatsky@chromium.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®