[<prev] [next>] [day] [month] [year] [list]
Message-ID: <tencent_D85C91225CB9F5A85A2141BD8C4E12E6D009@qq.com>
Date: Fri, 5 Dec 2025 14:38:55 +0800
From: xiaopeitux@...mail.com
To: ansuelsmth@...il.com,
ilia.lin@...nel.org,
rafael@...nel.org,
linux-arm-msm@...r.kernel.org,
linux-pm@...r.kernel.org,
linux-kernel@...r.kernel.org
Cc: Pei Xiao <xiaopei01@...inos.cn>
Subject: [PATCH] cpufreq: qcom-nvmem: add sentinel to qcom_cpufreq_ipq806x_match_list
From: Pei Xiao <xiaopei01@...inos.cn>
The of_device_id table is expected to be NULL-terminated. Without the
sentinel, the traversal of the array can lead to out-of-bound access,
causing undefined behavior.
This adds the missing sentinel to the qcom_cpufreq_ipq806x_match_list
array.
Fixes: 58f5d39d5ed8 ("cpufreq: qcom-nvmem: add compatible fallback for ipq806x for no SMEM")
Signed-off-by: Pei Xiao <xiaopei01@...inos.cn>
---
drivers/cpufreq/qcom-cpufreq-nvmem.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/cpufreq/qcom-cpufreq-nvmem.c b/drivers/cpufreq/qcom-cpufreq-nvmem.c
index 81e16b5a0245..66d3169b2331 100644
--- a/drivers/cpufreq/qcom-cpufreq-nvmem.c
+++ b/drivers/cpufreq/qcom-cpufreq-nvmem.c
@@ -263,6 +263,7 @@ static const struct of_device_id qcom_cpufreq_ipq806x_match_list[] __maybe_unuse
{ .compatible = "qcom,ipq8066", .data = (const void *)QCOM_ID_IPQ8066 },
{ .compatible = "qcom,ipq8068", .data = (const void *)QCOM_ID_IPQ8068 },
{ .compatible = "qcom,ipq8069", .data = (const void *)QCOM_ID_IPQ8069 },
+ { /* sentinel */ },
};
static int qcom_cpufreq_ipq8064_name_version(struct device *cpu_dev,
--
2.25.1
Powered by blists - more mailing lists