From: tip-bot for Ethan Barnes <tipbot@zytor.com>
To: linux-tip-commits@vger.kernel.org
Cc: srivatsa@mit.edu, bigeasy@linutronix.d, mingo@kernel.or,
mingo@kernel.org, tglx@linutronix.de,
linux-kernel@vger.kernel.org, Ethan.Barnes@wdc.com,
hpa@zytor.com, paulmck@linux.vnet.ibm.com,
ethan.barnes@sandisk.com
Subject: [tip:smp/hotplug] smp/hotplug: Handle removal correctly in cpuhp_store_callbacks()
Date: Thu, 20 Jul 2017 07:49:09 -0700 [thread overview]
Message-ID: <tip-0c96b27305faf06c068b45e07d28336c80dac286@git.kernel.org> (raw)
In-Reply-To: <DM2PR04MB398242FC7776D603D9F99C894A60@DM2PR04MB398.namprd04.prod.outlook.com>
Commit-ID: 0c96b27305faf06c068b45e07d28336c80dac286
Gitweb: http://git.kernel.org/tip/0c96b27305faf06c068b45e07d28336c80dac286
Author: Ethan Barnes <Ethan.Barnes@wdc.com>
AuthorDate: Wed, 19 Jul 2017 22:36:00 +0000
Committer: Thomas Gleixner <tglx@linutronix.de>
CommitDate: Thu, 20 Jul 2017 16:40:24 +0200
smp/hotplug: Handle removal correctly in cpuhp_store_callbacks()
If cpuhp_store_callbacks() is called for CPUHP_AP_ONLINE_DYN or
CPUHP_BP_PREPARE_DYN, which are the indicators for dynamically allocated
states, then cpuhp_store_callbacks() allocates a new dynamic state. The
first allocation in each range returns CPUHP_AP_ONLINE_DYN or
CPUHP_BP_PREPARE_DYN.
If cpuhp_remove_state() is invoked for one of these states, then there is
no protection against the allocation mechanism. So the removal, which
should clear the callbacks and the name, gets a new state assigned and
clears that one.
As a consequence the state which should be cleared stays initialized. A
consecutive CPU hotplug operation dereferences the state callbacks and
accesses either freed or reused memory, resulting in crashes.
Add a protection against this by checking the name argument for NULL. If
it's NULL it's a removal. If not, it's an allocation.
[ tglx: Added a comment and massaged changelog ]
Fixes: 5b7aa87e0482 ("cpu/hotplug: Implement setup/removal interface")
Signed-off-by: Ethan Barnes <ethan.barnes@sandisk.com>
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Cc: Ingo Molnar <mingo@kernel.or>
Cc: "Srivatsa S. Bhat" <srivatsa@mit.edu>
Cc: Sebastian Siewior <bigeasy@linutronix.d>
Cc: Paul McKenney <paulmck@linux.vnet.ibm.com>
Cc: stable@vger.kernel.org
Link: http://lkml.kernel.org/r/DM2PR04MB398242FC7776D603D9F99C894A60@DM2PR04MB398.namprd04.prod.outlook.com
---
kernel/cpu.c | 12 +++++++++++-
1 file changed, 11 insertions(+), 1 deletion(-)
diff --git a/kernel/cpu.c b/kernel/cpu.c
index eee0331..a88c29a 100644
--- a/kernel/cpu.c
+++ b/kernel/cpu.c
@@ -1252,7 +1252,17 @@ static int cpuhp_store_callbacks(enum cpuhp_state state, const char *name,
struct cpuhp_step *sp;
int ret = 0;
- if (state == CPUHP_AP_ONLINE_DYN || state == CPUHP_BP_PREPARE_DYN) {
+ /*
+ * If name is NULL, then the state gets removed.
+ *
+ * CPUHP_AP_ONLINE_DYN and CPUHP_BP_PREPARE_DYN are handed out on
+ * the first allocation from these dynamic ranges, so the removal
+ * would trigger a new allocation and clear the wrong (already
+ * empty) state, leaving the callbacks of the to be cleared state
+ * dangling, which causes wreckage on the next hotplug operation.
+ */
+ if (name && (state == CPUHP_AP_ONLINE_DYN ||
+ state == CPUHP_BP_PREPARE_DYN)) {
ret = cpuhp_reserve_state(state);
if (ret < 0)
return ret;
prev parent reply other threads:[~2017-07-20 14:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-19 22:36 [PATCH] cpu hotplug: Prevent Page Fault in cpuhp_remove_callbacks() Ethan Barnes
2017-07-20 14:05 ` Thomas Gleixner
2017-07-20 14:49 ` tip-bot for Ethan Barnes [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=tip-0c96b27305faf06c068b45e07d28336c80dac286@git.kernel.org \
--to=tipbot@zytor.com \
--cc=Ethan.Barnes@wdc.com \
--cc=bigeasy@linutronix.d \
--cc=ethan.barnes@sandisk.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@kernel.or \
--cc=mingo@kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=srivatsa@mit.edu \
--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
Powered by JetHome