From: Dawei Li <dawei.li@shingroup.cn>
To: will@kernel.org, mark.rutland@arm.com, yury.norov@gmail.com,
linux@rasmusvillemoes.dk
Cc: xueshuai@linux.alibaba.com, renyu.zj@linux.alibaba.com,
yangyicong@hisilicon.com, jonathan.cameron@huawei.com,
andersson@kernel.org, konrad.dybcio@linaro.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
Dawei Li <dawei.li@shingroup.cn>
Subject: [PATCH v2 07/10] perf/hisi_pcie: Avoid placing cpumask var on stack
Date: Wed, 3 Apr 2024 20:51:06 +0800 [thread overview]
Message-ID: <20240403125109.2054881-8-dawei.li@shingroup.cn> (raw)
In-Reply-To: <20240403125109.2054881-1-dawei.li@shingroup.cn>
For CONFIG_CPUMASK_OFFSTACK=y kernel, explicit allocation of cpumask
variable on stack is not recommended since it can cause potential stack
overflow.
Instead, kernel code should always use *cpumask_var API(s) to allocate
cpumask var in config-neutral way, leaving allocation strategy to
CONFIG_CPUMASK_OFFSTACK.
But dynamic allocation in cpuhp's teardown callback is somewhat problematic
for if allocation fails(which is unlikely but still possible):
- If -ENOMEM is returned to caller, kernel crashes for non-bringup
teardown;
- If callback pretends nothing happened and returns 0 to caller, it may
trap system into an in-consisitent/compromised state;
Use newly-introduced cpumask_any_and_but() to address all issues above.
It eliminates usage of temporary cpumask var in generic way, no matter how
the cpumask var is allocated.
Suggested-by: Mark Rutland <mark.rutland@arm.com>
Signed-off-by: Dawei Li <dawei.li@shingroup.cn>
---
drivers/perf/hisilicon/hisi_pcie_pmu.c | 9 ++++-----
1 file changed, 4 insertions(+), 5 deletions(-)
diff --git a/drivers/perf/hisilicon/hisi_pcie_pmu.c b/drivers/perf/hisilicon/hisi_pcie_pmu.c
index 5d1f0e9fdb08..06b192cc31d5 100644
--- a/drivers/perf/hisilicon/hisi_pcie_pmu.c
+++ b/drivers/perf/hisilicon/hisi_pcie_pmu.c
@@ -673,7 +673,6 @@ static int hisi_pcie_pmu_offline_cpu(unsigned int cpu, struct hlist_node *node)
{
struct hisi_pcie_pmu *pcie_pmu = hlist_entry_safe(node, struct hisi_pcie_pmu, node);
unsigned int target;
- cpumask_t mask;
int numa_node;
/* Nothing to do if this CPU doesn't own the PMU */
@@ -684,10 +683,10 @@ static int hisi_pcie_pmu_offline_cpu(unsigned int cpu, struct hlist_node *node)
/* Choose a local CPU from all online cpus. */
numa_node = dev_to_node(&pcie_pmu->pdev->dev);
- if (cpumask_and(&mask, cpumask_of_node(numa_node), cpu_online_mask) &&
- cpumask_andnot(&mask, &mask, cpumask_of(cpu)))
- target = cpumask_any(&mask);
- else
+
+ target = cpumask_any_and_but(cpumask_of_node(numa_node),
+ cpu_online_mask, cpu);
+ if (target >= nr_cpu_ids)
target = cpumask_any_but(cpu_online_mask, cpu);
if (target >= nr_cpu_ids) {
--
2.27.0
next prev parent reply other threads:[~2024-04-03 12:54 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-03 12:50 [PATCH v2 00/10] perf: Avoid placing cpumask var on stack Dawei Li
2024-04-03 12:51 ` [PATCH v2 01/10] cpumask: add cpumask_any_and_but() Dawei Li
2024-04-03 12:51 ` [PATCH v2 02/10] perf/alibaba_uncore_drw: Avoid placing cpumask var on stack Dawei Li
2024-04-03 14:16 ` Mark Rutland
2024-04-03 12:51 ` [PATCH v2 03/10] perf/arm-cmn: " Dawei Li
2024-04-03 14:23 ` Mark Rutland
2024-04-03 12:51 ` [PATCH v2 04/10] perf/arm_cspmu: " Dawei Li
2024-04-03 14:21 ` Mark Rutland
2024-04-03 12:51 ` [PATCH v2 05/10] perf/arm_dsu: " Dawei Li
2024-04-03 14:32 ` Mark Rutland
2024-04-03 12:51 ` [PATCH v2 06/10] perf/dwc_pcie: " Dawei Li
2024-04-03 14:33 ` Mark Rutland
2024-04-03 12:51 ` Dawei Li [this message]
2024-04-03 14:35 ` [PATCH v2 07/10] perf/hisi_pcie: " Mark Rutland
2024-04-05 9:52 ` Jonathan Cameron
2024-04-03 12:51 ` [PATCH v2 08/10] perf/hisi_uncore: " Dawei Li
2024-04-03 14:35 ` Mark Rutland
2024-04-05 9:53 ` Jonathan Cameron
2024-04-03 12:51 ` [PATCH v2 09/10] perf/qcom_l2: " Dawei Li
2024-04-03 14:36 ` Mark Rutland
2024-04-03 12:51 ` [PATCH v2 10/10] perf/thunderx2: " Dawei Li
2024-04-03 14:38 ` Mark Rutland
2024-04-03 14:41 ` [PATCH v2 00/10] perf: " Mark Rutland
2024-04-03 16:11 ` Dawei Li
2024-04-03 16:39 ` Yury Norov
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=20240403125109.2054881-8-dawei.li@shingroup.cn \
--to=dawei.li@shingroup.cn \
--cc=andersson@kernel.org \
--cc=jonathan.cameron@huawei.com \
--cc=konrad.dybcio@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=mark.rutland@arm.com \
--cc=renyu.zj@linux.alibaba.com \
--cc=will@kernel.org \
--cc=xueshuai@linux.alibaba.com \
--cc=yangyicong@hisilicon.com \
--cc=yury.norov@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