From: Johan Hovold <johan@kernel.org>
To: Gabor Juhos <j4g8y7@gmail.com>
Cc: Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
Sricharan Ramabadhran <quic_srichara@quicinc.com>,
Varadarajan Narayanan <quic_varada@quicinc.com>,
Gokul Sriram Palanisamy <quic_gokulsri@quicinc.com>,
Devi Priya <quic_devipriy@quicinc.com>,
Anusha Rao <quic_anusha@quicinc.com>,
Bryan O'Donoghue <bryan.odonoghue@linaro.org>,
Georgi Djakov <gdjakov@mm-sol.com>,
linux-arm-msm@vger.kernel.org, linux-clk@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/7] clk: qcom: gcc-ipq5018: fix terminating of frequency table arrays
Date: Fri, 1 Mar 2024 15:03:15 +0100 [thread overview]
Message-ID: <ZeHgI2nsADrkecC8@hovoldconsulting.com> (raw)
In-Reply-To: <91b36da5-637d-4156-8be4-5aed55fc3c5d@gmail.com>
On Fri, Mar 01, 2024 at 02:37:01PM +0100, Gabor Juhos wrote:
> Hi Johan,
>
> 2024. 03. 01. 10:40 keltezéssel, Johan Hovold írta:
> > On Thu, Feb 29, 2024 at 07:07:46PM +0100, Gabor Juhos wrote:
> >> The frequency table arrays are supposed to be terminated with an
> >> empty element. Add such entry to the end of the arrays where it
> >> is missing in order to avoid possible out-of-bound access when
> >> the table is traversed by functions like qcom_find_freq() or
> >> qcom_find_freq_floor().
> >>
> >> Fixes: e3fdbef1bab8 ("clk: qcom: Add Global Clock controller (GCC) driver for IPQ5018")
> >
> > Good find!
> >
> > Looks like these should be backported to the stable kernels as well so
> > someone should add:
> >
> > Cc: stable@vger.kernel.org
> >
> > to all patches except possibly the sc8280xp one (that camera clock
> > controller was added in 6.8-rc1 so that patch does not need it in case
> > you can these fixes in before 6.8 is released).
>
> You are right maybe, although I did not find strong enough reasons for adding
> the stable tags.
>
> Only the changes of the gcc-ipq5018 driver has been tested on real hardware the
> others are not. So those does not fit into the "It must be obviously correct and
> tested." rule.
Since this looks like a straight-forward and obviously correct fix for a
bug which could have bad consequences, not being able to test each patch
on actual hardware is not a problem.
Johan
next prev parent reply other threads:[~2024-03-01 14:03 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-29 18:07 [PATCH 0/7] clk: qcom: fix frequency table termination in several drivers Gabor Juhos
2024-02-29 18:07 ` [PATCH 1/7] clk: qcom: gcc-ipq5018: fix terminating of frequency table arrays Gabor Juhos
2024-03-01 1:16 ` Stephen Boyd
2024-03-01 9:40 ` Johan Hovold
2024-03-01 13:37 ` Gabor Juhos
2024-03-01 14:03 ` Johan Hovold [this message]
2024-03-02 18:41 ` Bjorn Andersson
2024-02-29 18:07 ` [PATCH 2/7] clk: qcom: gcc-ipq6018: " Gabor Juhos
2024-03-01 1:17 ` Stephen Boyd
2024-02-29 18:07 ` [PATCH 3/7] clk: qcom: gcc-ipq8074: " Gabor Juhos
2024-03-01 1:18 ` Stephen Boyd
2024-02-29 18:07 ` [PATCH 4/7] clk: qcom: gcc-ipq9574: " Gabor Juhos
2024-03-01 1:18 ` Stephen Boyd
2024-02-29 18:07 ` [PATCH 5/7] clk: qcom: camcc-sc8280xp: " Gabor Juhos
2024-03-01 1:19 ` Stephen Boyd
2024-02-29 18:07 ` [PATCH 6/7] clk: qcom: mmcc-apq8084: " Gabor Juhos
2024-03-01 1:19 ` Stephen Boyd
2024-02-29 18:07 ` [PATCH 7/7] clk: qcom: mmcc-msm8974: " Gabor Juhos
2024-03-01 1:20 ` Stephen Boyd
2024-03-03 19:50 ` [PATCH 0/7] clk: qcom: fix frequency table termination in several drivers Bjorn Andersson
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=ZeHgI2nsADrkecC8@hovoldconsulting.com \
--to=johan@kernel.org \
--cc=andersson@kernel.org \
--cc=bryan.odonoghue@linaro.org \
--cc=gdjakov@mm-sol.com \
--cc=j4g8y7@gmail.com \
--cc=konrad.dybcio@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=quic_anusha@quicinc.com \
--cc=quic_devipriy@quicinc.com \
--cc=quic_gokulsri@quicinc.com \
--cc=quic_srichara@quicinc.com \
--cc=quic_varada@quicinc.com \
--cc=sboyd@kernel.org \
/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