From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: deepthi@linux.vnet.ibm.com
Cc: linux-kernel@vger.kernel.org, lenb@kernel.org,
linux-acpi@vger.kernel.org
Subject: [PATCH RFC] acpi: Fix unprotected smp_processor_id() in acpi_processor_cst_has_changed()
Date: Thu, 23 Feb 2012 12:58:05 -0800 [thread overview]
Message-ID: <20120223205805.GA31838@linux.vnet.ibm.com> (raw)
The acpi_processor_cst_has_changed() function is invoked from a
CPU_ONLINE or CPU_DEAD function, which might well execute on CPU 0
even though the CPU being hotplugged is some other CPU. In addition,
acpi_processor_cst_has_changed() invokes smp_processor_id() without
protection, resulting in splats when onlining CPUs.
This commit therefore changes the smp_processor_id() to pr->id, as is
used elsewhere in the code, for example, in acpi_processor_add().
This works for me, but I don't claim to understand ACPI.
Signed-off-by: Paul E. McKenney <paul.mckenney@linaro.org>
diff --git a/drivers/acpi/processor_idle.c b/drivers/acpi/processor_idle.c
index 0e8e2de..9e57b06 100644
--- a/drivers/acpi/processor_idle.c
+++ b/drivers/acpi/processor_idle.c
@@ -1159,8 +1159,7 @@ int acpi_processor_cst_has_changed(struct acpi_processor *pr)
* to make the code that updates C-States be called once.
*/
- if (smp_processor_id() == 0 &&
- cpuidle_get_driver() == &acpi_idle_driver) {
+ if (pr->id == 0 && cpuidle_get_driver() == &acpi_idle_driver) {
cpuidle_pause_and_lock();
/* Protect against cpu-hotplug */
next reply other threads:[~2012-02-23 20:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-23 20:58 Paul E. McKenney [this message]
2012-02-28 6:13 ` [PATCH RFC] acpi: Fix unprotected smp_processor_id() in acpi_processor_cst_has_changed() Srivatsa S. Bhat
2012-02-28 7:19 ` Yong Zhang
2012-02-28 13:30 ` Paul E. McKenney
2012-02-28 20:57 ` Rafael J. Wysocki
2012-02-28 21:27 ` Paul E. McKenney
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=20120223205805.GA31838@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=deepthi@linux.vnet.ibm.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).