From: Vaidyanathan Srinivasan <svaidy@linux.vnet.ibm.com>
To: Michael Neuling <mikey@neuling.org>,
Michael Ellerman <mpe@ellerman.id.au>,
"Rafael J . Wysocki" <rjw@rjwysocki.net>,
Daniel Lezcano <daniel.lezcano@linaro.org>
Cc: linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org,
linux-pm@vger.kernel.org
Subject: [PATCH v1 0/2] cpuidle: Fixes in cpuidle driver
Date: Thu, 23 Mar 2017 20:52:45 +0530 [thread overview]
Message-ID: <20170323152247.14733-1-svaidy@linux.vnet.ibm.com> (raw)
When CONFIG_HOTPLUG_CPU=n and cpu_present is less than cpu_possible,
then cpuidle-powernv not passing an explicit drv->cpu_mask allows
generic cpuidle driver to try create sysfs objects for cpus that does
not have cpu_devices created by calling register_cpu().
This caused kernel to access incorrect address and crash. The
following patch series fixes the cpuidle-powernv driver and also adds
additional checks in cpuidle_add_sysfs()
This patch set is against v4.11-rc3.
Changed from v1: Updated commit message and comments.
Signed-off-by: Vaidyanathan Srinivasan <svaidy@linux.vnet.ibm.com>
next reply other threads:[~2017-03-23 15:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-23 15:22 Vaidyanathan Srinivasan [this message]
2017-03-23 15:22 ` [PATCH v2 1/2] powerpc/powernv/cpuidle: Pass correct drv->cpumask for registration Vaidyanathan Srinivasan
2017-03-23 15:28 ` Rafael J. Wysocki
2017-03-23 15:42 ` Vaidyanathan Srinivasan
2017-03-27 10:38 ` Michael Ellerman
2017-03-24 8:29 ` Gautham R Shenoy
2017-03-23 15:22 ` [PATCH v2 2/2] cpuidle: Validate cpu_dev in cpuidle_add_sysfs Vaidyanathan Srinivasan
2017-03-23 15:27 ` Rafael J. Wysocki
2017-03-23 15:40 ` Vaidyanathan Srinivasan
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=20170323152247.14733-1-svaidy@linux.vnet.ibm.com \
--to=svaidy@linux.vnet.ibm.com \
--cc=daniel.lezcano@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mikey@neuling.org \
--cc=mpe@ellerman.id.au \
--cc=rjw@rjwysocki.net \
/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).