[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <74xcws6rns5hrmkf4hsfuittgzsddsc3hnqj6jbfsfu3o2vvol@gy32jyg75gmd>
Date: Wed, 26 Feb 2025 15:24:45 +0100
From: Jiri Pirko <jiri@...nulli.us>
To: Jiasheng Jiang <jiashengjiangcool@...il.com>
Cc: arkadiusz.kubalewski@...el.com, davem@...emloft.net,
jan.glaza@...el.com, linux-kernel@...r.kernel.org, netdev@...r.kernel.org,
przemyslaw.kitszel@...el.com, stable@...r.kernel.org, vadim.fedorenko@...ux.dev
Subject: Re: [PATCH v2] dpll: Add an assertion to check freq_supported_num
Wed, Feb 26, 2025 at 04:09:30AM +0100, jiashengjiangcool@...il.com wrote:
>Since the driver is broken in the case that src->freq_supported is not
>NULL but src->freq_supported_num is 0, add an assertion for it.
>
>Fixes: 830ead5fb0c5 ("dpll: fix pin dump crash for rebound module")
It's not a real bug in current kernel. I don't think it's worth "fixes"
line and -net tree. I think it should be just sent to -net-next.
>Cc: <stable@...r.kernel.org> # v6.8+
>Signed-off-by: Jiasheng Jiang <jiashengjiangcool@...il.com>
>---
>Changelog:
>
>v1 -> v2:
>
>1. Replace the check with an assertion.
>---
> drivers/dpll/dpll_core.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
>diff --git a/drivers/dpll/dpll_core.c b/drivers/dpll/dpll_core.c
>index 32019dc33cca..3296776c1ebb 100644
>--- a/drivers/dpll/dpll_core.c
>+++ b/drivers/dpll/dpll_core.c
>@@ -443,8 +443,9 @@ static void dpll_pin_prop_free(struct dpll_pin_properties *prop)
> static int dpll_pin_prop_dup(const struct dpll_pin_properties *src,
> struct dpll_pin_properties *dst)
> {
>+ BUG_ON(src->freq_supported && !src->freq_supported_num);
Warnon-return please.
> memcpy(dst, src, sizeof(*dst));
>- if (src->freq_supported && src->freq_supported_num) {
>+ if (src->freq_supported) {
> size_t freq_size = src->freq_supported_num *
> sizeof(*src->freq_supported);
> dst->freq_supported = kmemdup(src->freq_supported,
>--
>2.25.1
>
Powered by blists - more mailing lists