From: Andi Kleen <andi@firstfloor.org>
To: torvalds@osdl.org, linux-kernel@vger.kernel.org
Subject: [PATCH] [2/2] Don't complain about disabled irqs when the system has paniced
Date: Tue, 2 Sep 2008 15:49:23 +0200 (CEST) [thread overview]
Message-ID: <20080902134923.9A7EF3E6A01@basil.firstfloor.org> (raw)
In-Reply-To: <20080902349.573187695@firstfloor.org>
panic calls smp_send_stop which eventually calls smp_call_function_*.
smp_call_function warns about disabled interrupts. But it's legal
to call panic in this case. When this happens panic() prints
several ugly backtraces. So don't check for disabled interrupts
in panic state.
Signed-off-by: Andi Kleen <ak@linux.intel.com>
Index: linux/kernel/smp.c
===================================================================
--- linux.orig/kernel/smp.c
+++ linux/kernel/smp.c
@@ -216,7 +216,7 @@ int smp_call_function_single(int cpu, vo
int err = 0;
/* Can deadlock when called with interrupts disabled */
- WARN_ON(irqs_disabled());
+ WARN_ON(system_state < SYSTEM_PANIC && irqs_disabled());
if (cpu == me) {
local_irq_save(flags);
@@ -260,7 +260,8 @@ EXPORT_SYMBOL(smp_call_function_single);
void __smp_call_function_single(int cpu, struct call_single_data *data)
{
/* Can deadlock when called with interrupts disabled */
- WARN_ON((data->flags & CSD_FLAG_WAIT) && irqs_disabled());
+ WARN_ON(system_state < SYSTEM_PANIC &&
+ (data->flags & CSD_FLAG_WAIT) && irqs_disabled());
generic_exec_single(cpu, data);
}
@@ -329,7 +330,7 @@ int smp_call_function_mask(cpumask_t mas
int slowpath = 0;
/* Can deadlock when called with interrupts disabled */
- WARN_ON(irqs_disabled());
+ WARN_ON(system_state < SYSTEM_PANIC && irqs_disabled());
cpu = smp_processor_id();
allbutself = cpu_online_map;
next prev parent reply other threads:[~2008-09-02 13:50 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-02 13:49 [PATCH] [0/2] Fix panic regression in 2.6.27 Andi Kleen
2008-09-02 13:49 ` [PATCH] [1/2] Add a SYSTEM_PANIC state Andi Kleen
2008-09-03 19:04 ` Andrew Morton
2008-09-03 19:16 ` Andi Kleen
2008-09-03 19:32 ` Andrew Morton
2008-09-03 19:44 ` Andi Kleen
2008-09-02 13:49 ` Andi Kleen [this message]
2008-09-02 14:28 ` [PATCH] [2/2] Don't complain about disabled irqs when the system has paniced Peter Zijlstra
2008-09-02 14:40 ` Andi Kleen
2008-09-02 14:45 ` Peter Zijlstra
2008-09-02 15:00 ` Andi Kleen
2008-09-03 6:02 ` Nick Piggin
2008-09-03 6:59 ` Andi Kleen
2008-09-03 9:37 ` Nick Piggin
2008-09-03 9:48 ` Andi Kleen
2008-09-03 10:17 ` Nick Piggin
2008-09-03 10:26 ` Jens Axboe
2008-09-12 19:50 ` Pavel Machek
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=20080902134923.9A7EF3E6A01@basil.firstfloor.org \
--to=andi@firstfloor.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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®