From: Peter Zijlstra <peterz@infradead.org>
To: Andrew Murray <andrew.murray@arm.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Rik van Riel <riel@surriel.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] smp,cpumask: Don't call functions on offline CPUs
Date: Wed, 22 May 2019 16:09:21 +0200 [thread overview]
Message-ID: <20190522140921.GD16275@worktop.programming.kicks-ass.net> (raw)
In-Reply-To: <20190522111537.27815-1-andrew.murray@arm.com>
On Wed, May 22, 2019 at 12:15:37PM +0100, Andrew Murray wrote:
> 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.
I'm confused, why are you feeding it offline CPUs to begin with? @mask
shouldn't include them.
Is perhaps the problem that on_each_cpu_cond() uses cpu_onlne_mask
without protection?
Something like so?
diff --git a/kernel/smp.c b/kernel/smp.c
index f4cf1b0bb3b8..a493b3dfa67f 100644
--- a/kernel/smp.c
+++ b/kernel/smp.c
@@ -705,8 +707,10 @@ void on_each_cpu_cond(bool (*cond_func)(int cpu, void *info),
smp_call_func_t func, void *info, bool wait,
gfp_t gfp_flags)
{
+ cpus_read_lock();
on_each_cpu_cond_mask(cond_func, func, info, wait, gfp_flags,
cpu_online_mask);
+ cpus_read_unlock();
}
EXPORT_SYMBOL(on_each_cpu_cond);
next prev parent reply other threads:[~2019-05-22 14:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-22 11:15 [PATCH] smp,cpumask: Don't call functions on offline CPUs Andrew Murray
2019-05-22 14:09 ` Peter Zijlstra [this message]
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=20190522140921.GD16275@worktop.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=andrew.murray@arm.com \
--cc=linux-kernel@vger.kernel.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