From: Stephen Brennan <stephen.s.brennan@oracle.com>
To: Petr Mladek <pmladek@suse.com>,
Sergey Senozhatsky <senozhatsky@chromium.org>,
Steven Rostedt <rostedt@goodmis.org>,
John Ogness <john.ogness@linutronix.de>
Cc: Stephen Brennan <stephen.s.brennan@oracle.com>,
Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
linux-kernel@vger.kernel.org
Subject: [PATCH 1/4] panic: Add panic_in_progress helper
Date: Fri, 21 Jan 2022 11:02:19 -0800 [thread overview]
Message-ID: <20220121190222.572694-2-stephen.s.brennan@oracle.com> (raw)
In-Reply-To: <20220121190222.572694-1-stephen.s.brennan@oracle.com>
Suggested-by: Petr Mladek <pmladek@suse.com>
Signed-off-by: Stephen Brennan <stephen.s.brennan@oracle.com>
---
We cannot define a static inline without including linux/atomic.h, so
I just added a macro for convenience in later patches. Since macros were
the only option, I didn't include a helper for
panic_in_progress_different_cpu().
include/linux/panic.h | 3 +++
1 file changed, 3 insertions(+)
diff --git a/include/linux/panic.h b/include/linux/panic.h
index f5844908a089..8e8bd50494d5 100644
--- a/include/linux/panic.h
+++ b/include/linux/panic.h
@@ -45,6 +45,9 @@ extern bool crash_kexec_post_notifiers;
extern atomic_t panic_cpu;
#define PANIC_CPU_INVALID -1
+#define panic_in_progress() \
+ unlikely(atomic_read(&panic_cpu) != PANIC_CPU_INVALID)
+
/*
* Only to be used by arch init code. If the user over-wrote the default
* CONFIG_PANIC_TIMEOUT, honor it.
--
2.30.2
next prev parent reply other threads:[~2022-01-21 19:02 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-21 19:02 [PATCH 0/4] printk: reduce deadlocks during panic Stephen Brennan
2022-01-21 19:02 ` Stephen Brennan [this message]
2022-01-25 11:48 ` [PATCH 1/4] panic: Add panic_in_progress helper Petr Mladek
2022-01-26 17:37 ` Stephen Brennan
2022-01-21 19:02 ` [PATCH 2/4] printk: disable optimistic spin during panic Stephen Brennan
2022-01-25 12:42 ` Petr Mladek
2022-01-26 9:18 ` Sergey Senozhatsky
2022-01-26 9:45 ` John Ogness
2022-01-26 10:06 ` Sergey Senozhatsky
2022-01-26 18:15 ` Stephen Brennan
2022-01-27 7:11 ` Sergey Senozhatsky
2022-01-27 9:09 ` John Ogness
2022-01-27 11:38 ` Petr Mladek
2022-01-27 12:43 ` John Ogness
2022-01-27 14:25 ` Petr Mladek
2022-01-21 19:02 ` [PATCH 3/4] printk: Avoid livelock with heavy printk " Stephen Brennan
2022-01-25 14:25 ` Petr Mladek
2022-01-21 19:02 ` [PATCH 4/4] printk: Drop console_sem " Stephen Brennan
2022-01-24 16:12 ` John Ogness
2022-01-24 16:26 ` John Ogness
2022-01-25 15:04 ` 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=20220121190222.572694-2-stephen.s.brennan@oracle.com \
--to=stephen.s.brennan@oracle.com \
--cc=john.ogness@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=senozhatsky@chromium.org \
--cc=sergey.senozhatsky@gmail.com \
/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®