From: Eric Biggers <ebiggers@kernel.org>
To: stable@vger.kernel.org
Cc: Harshit Mogalapalli <harshit.m.mogalapalli@oracle.com>,
Kees Cook <keescook@chromium.org>, SeongJae Park <sj@kernel.org>,
Seth Jenkins <sethjenkins@google.com>,
Jann Horn <jannh@google.com>,
"Eric W . Biederman" <ebiederm@xmission.com>,
linux-hardening@vger.kernel.org, linux-kernel@vger.kernel.org,
Andrey Ryabinin <ryabinin.a.a@gmail.com>,
Baoquan He <bhe@redhat.com>, Jonathan Corbet <corbet@lwn.net>,
Xuefeng Li <lixuefeng@loongson.cn>,
Tiezhu Yang <yangtiezhu@loongson.cn>,
Marco Elver <elver@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: [PATCH 4.14 v2 02/15] panic: unset panic_on_warn inside panic()
Date: Thu, 2 Feb 2023 16:33:41 -0800 [thread overview]
Message-ID: <20230203003354.85691-3-ebiggers@kernel.org> (raw)
In-Reply-To: <20230203003354.85691-1-ebiggers@kernel.org>
From: Tiezhu Yang <yangtiezhu@loongson.cn>
commit 1a2383e8b84c0451fd9b1eec3b9aab16f30b597c upstream.
In the current code, the following three places need to unset
panic_on_warn before calling panic() to avoid recursive panics:
kernel/kcsan/report.c: print_report()
kernel/sched/core.c: __schedule_bug()
mm/kfence/report.c: kfence_report_error()
In order to avoid copy-pasting "panic_on_warn = 0" all over the places,
it is better to move it inside panic() and then remove it from the other
places.
Link: https://lkml.kernel.org/r/1644324666-15947-4-git-send-email-yangtiezhu@loongson.cn
Signed-off-by: Tiezhu Yang <yangtiezhu@loongson.cn>
Reviewed-by: Marco Elver <elver@google.com>
Cc: Andrey Ryabinin <ryabinin.a.a@gmail.com>
Cc: Baoquan He <bhe@redhat.com>
Cc: Jonathan Corbet <corbet@lwn.net>
Cc: Xuefeng Li <lixuefeng@loongson.cn>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Signed-off-by: Eric Biggers <ebiggers@google.com>
---
kernel/panic.c | 20 +++++++++++---------
1 file changed, 11 insertions(+), 9 deletions(-)
diff --git a/kernel/panic.c b/kernel/panic.c
index 207ceac3a432e..bd7c3ea3bf1e6 100644
--- a/kernel/panic.c
+++ b/kernel/panic.c
@@ -139,6 +139,16 @@ void panic(const char *fmt, ...)
int old_cpu, this_cpu;
bool _crash_kexec_post_notifiers = crash_kexec_post_notifiers;
+ if (panic_on_warn) {
+ /*
+ * This thread may hit another WARN() in the panic path.
+ * Resetting this prevents additional WARN() from panicking the
+ * system on this thread. Other threads are blocked by the
+ * panic_mutex in panic().
+ */
+ panic_on_warn = 0;
+ }
+
/*
* Disable local interrupts. This will prevent panic_smp_self_stop
* from deadlocking the first cpu that invokes the panic, since
@@ -536,16 +546,8 @@ void __warn(const char *file, int line, void *caller, unsigned taint,
if (args)
vprintk(args->fmt, args->args);
- if (panic_on_warn) {
- /*
- * This thread may hit another WARN() in the panic path.
- * Resetting this prevents additional WARN() from panicking the
- * system on this thread. Other threads are blocked by the
- * panic_mutex in panic().
- */
- panic_on_warn = 0;
+ if (panic_on_warn)
panic("panic_on_warn set ...\n");
- }
print_modules();
--
2.39.1
next prev parent reply other threads:[~2023-02-03 0:35 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-03 0:33 [PATCH 4.14 v2 00/15] Backport oops_limit to 4.14 Eric Biggers
2023-02-03 0:33 ` [PATCH 4.14 v2 01/15] sysctl: add a new register_sysctl_init() interface Eric Biggers
2023-02-03 0:33 ` Eric Biggers [this message]
2023-02-03 0:33 ` [PATCH 4.14 v2 03/15] exit: Add and use make_task_dead Eric Biggers
2023-02-03 0:33 ` [PATCH 4.14 v2 04/15] objtool: Add a missing comma to avoid string concatenation Eric Biggers
2023-02-03 0:33 ` [PATCH 4.14 v2 05/15] hexagon: Fix function name in die() Eric Biggers
2023-02-03 0:33 ` [PATCH 4.14 v2 06/15] h8300: Fix build errors from do_exit() to make_task_dead() transition Eric Biggers
2023-02-03 0:33 ` [PATCH 4.14 v2 07/15] ia64: make IA64_MCA_RECOVERY bool instead of tristate Eric Biggers
2023-02-03 0:33 ` [PATCH 4.14 v2 08/15] exit: Put an upper limit on how often we can oops Eric Biggers
2023-02-03 0:33 ` [PATCH 4.14 v2 09/15] exit: Expose "oops_count" to sysfs Eric Biggers
2023-02-03 0:33 ` [PATCH 4.14 v2 10/15] exit: Allow oops_limit to be disabled Eric Biggers
2023-02-03 0:33 ` [PATCH 4.14 v2 11/15] panic: Consolidate open-coded panic_on_warn checks Eric Biggers
2023-02-03 0:33 ` [PATCH 4.14 v2 12/15] panic: Introduce warn_limit Eric Biggers
2023-02-03 0:33 ` [PATCH 4.14 v2 13/15] panic: Expose "warn_count" to sysfs Eric Biggers
2023-02-03 0:33 ` [PATCH 4.14 v2 14/15] docs: Fix path paste-o for /sys/kernel/warn_count Eric Biggers
2023-02-03 0:33 ` [PATCH 4.14 v2 15/15] exit: Use READ_ONCE() for all oops/warn limit reads Eric Biggers
2023-02-03 7:57 ` [PATCH 4.14 v2 00/15] Backport oops_limit to 4.14 Greg KH
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=20230203003354.85691-3-ebiggers@kernel.org \
--to=ebiggers@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=bhe@redhat.com \
--cc=corbet@lwn.net \
--cc=ebiederm@xmission.com \
--cc=elver@google.com \
--cc=harshit.m.mogalapalli@oracle.com \
--cc=jannh@google.com \
--cc=keescook@chromium.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lixuefeng@loongson.cn \
--cc=ryabinin.a.a@gmail.com \
--cc=sethjenkins@google.com \
--cc=sj@kernel.org \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=yangtiezhu@loongson.cn \
/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;
as well as URLs for NNTP newsgroup(s).