From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: lenb@kernel.org, Yong Zhang <yong.zhang0@gmail.com>,
deepthi@linux.vnet.ibm.com, linux-kernel@vger.kernel.org,
linux-acpi@vger.kernel.org
Subject: Re: [PATCH RFC] acpi: Fix unprotected smp_processor_id() in acpi_processor_cst_has_changed()
Date: Tue, 28 Feb 2012 13:27:44 -0800 [thread overview]
Message-ID: <20120228212744.GL2465@linux.vnet.ibm.com> (raw)
In-Reply-To: <201202282157.53804.rjw@sisk.pl>
On Tue, Feb 28, 2012 at 09:57:53PM +0100, Rafael J. Wysocki wrote:
> On Tuesday, February 28, 2012, Paul E. McKenney wrote:
> > On Tue, Feb 28, 2012 at 03:19:43PM +0800, Yong Zhang wrote:
> > > On Thu, Feb 23, 2012 at 12:58:05PM -0800, Paul E. McKenney wrote:
> > > > 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>
> > >
> > > Got the same warning.
> > > And the patch works on my side.
> > >
> > > Tested-by: Yong Zhang <yong.zhang0@gmail.com>
> >
> > Thank you, I have added your Tested-by (and Srivatsa's Reviewed-by,
> > for that matter).
> >
> > Any takers for this, or should I just push it up the -tip tree?
>
> I think this patch is for Len, either through ACPI, or through the idle tree.
> Len?
Whichever way it is supposed to go, it reminds me of the need for it every
time I forget to merge it in before testing. ;-)
> Anyway:
>
> Acked-by: Rafael J. Wysocki <rjw@sisk.pl>
Thank you, applied! The patch appears below with the recent review,
testing, and ack.
Thanx, Paul
------------------------------------------------------------------------
acpi: Fix unprotected smp_processor_id() in acpi_processor_cst_has_changed()
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().
Signed-off-by: Paul E. McKenney <paul.mckenney@linaro.org>
Signed-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
Reviewed-by: Srivatsa S. Bhat <srivatsa.bhat@linux.vnet.ibm.com>
Tested-by: Yong Zhang <yong.zhang0@gmail.com>
Acked-by: Rafael J. Wysocki <rjw@sisk.pl>
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 */
prev parent reply other threads:[~2012-02-28 21:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-23 20:58 [PATCH RFC] acpi: Fix unprotected smp_processor_id() in acpi_processor_cst_has_changed() Paul E. McKenney
2012-02-28 6:13 ` 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 [this message]
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=20120228212744.GL2465@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 \
--cc=rjw@sisk.pl \
--cc=yong.zhang0@gmail.com \
/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).