From: Andrew Murray <andrew.murray@arm.com>
To: peterz@infradead.org, Thomas Gleixner <tglx@linutronix.de>
Cc: Rik van Riel <riel@surriel.com>, linux-kernel@vger.kernel.org
Subject: [PATCH] smp,cpumask: Don't call functions on offline CPUs
Date: Wed, 22 May 2019 12:15:37 +0100 [thread overview]
Message-ID: <20190522111537.27815-1-andrew.murray@arm.com> (raw)
When we are able to allocate a cpumask in on_each_cpu_cond_mask
we call functions with on_each_cpu_mask - this masks out offline
cpus via smp_call_function_many.
However when we fail to allocate a cpumask in on_each_cpu_cond_mask
we call functions with smp_call_function_single - this will return
-ENXIO from generic_exec_single if a CPU is offline which will
result in a WARN_ON_ONCE.
Let's avoid the WARN by only calling smp_call_function_single when
the CPU is online and thus making both paths consistent with each
other.
Signed-off-by: Andrew Murray <andrew.murray@arm.com>
---
kernel/smp.c | 8 ++++++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/kernel/smp.c b/kernel/smp.c
index f4cf1b0bb3b8..10970692f1c0 100644
--- a/kernel/smp.c
+++ b/kernel/smp.c
@@ -259,6 +259,7 @@ static void flush_smp_call_function_queue(bool warn_cpu_offline)
/*
* smp_call_function_single - Run a function on a specific CPU
+ * @cpu: The CPU to run on.
* @func: The function to run. This must be fast and non-blocking.
* @info: An arbitrary pointer to pass to the function.
* @wait: If true, wait until function has completed on other CPUs.
@@ -657,6 +658,8 @@ EXPORT_SYMBOL(on_each_cpu_mask);
* completed on other CPUs.
* @gfp_flags: GFP flags to use when allocating the cpumask
* used internally by the function.
+ * @mask: The set of cpus to run on (only runs on online
+ subset).
*
* The function might sleep if the GFP flags indicates a non
* atomic allocation is allowed.
@@ -690,12 +693,13 @@ void on_each_cpu_cond_mask(bool (*cond_func)(int cpu, void *info),
* just have to IPI them one by one.
*/
preempt_disable();
- for_each_cpu(cpu, mask)
- if (cond_func(cpu, info)) {
+ for_each_cpu(cpu, mask) {
+ if (cpu_online(cpu) && cond_func(cpu, info)) {
ret = smp_call_function_single(cpu, func,
info, wait);
WARN_ON_ONCE(ret);
}
+ }
preempt_enable();
}
}
--
2.21.0
next reply other threads:[~2019-05-22 11:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-22 11:15 Andrew Murray [this message]
2019-05-22 14:09 ` Peter Zijlstra
2019-05-22 14:37 ` Andrew Murray
2019-05-22 14:49 ` Peter Zijlstra
2019-05-22 15:14 ` Andrew Murray
2019-05-27 10:52 ` Peter Zijlstra
2019-05-22 18:23 ` Rik van Riel
2019-05-27 10:53 ` Peter Zijlstra
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=20190522111537.27815-1-andrew.murray@arm.com \
--to=andrew.murray@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=riel@surriel.com \
--cc=tglx@linutronix.de \
/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®