From: Stephen Boyd <sboyd@kernel.org>
To: Abel Vesa <abel.vesa@linaro.org>,
Bjorn Andersson <andersson@kernel.org>,
Bryan O'Donoghue <bryan.odonoghue@linaro.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Michael Turquette <mturquette@baylibre.com>,
Rajendra Nayak <quic_rjendra@quicinc.com>
Cc: linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-msm@vger.kernel.org,
Bryan O'Donoghue <bryan.odonoghue@linaro.org>
Subject: Re: [PATCH 1/2] clk: Fix clk_core_get NULL dereference
Date: Fri, 08 Mar 2024 16:36:13 -0800 [thread overview]
Message-ID: <b809a691de642231b687358eb4bc03aa.sboyd@kernel.org> (raw)
In-Reply-To: <20240302-linux-next-24-03-01-simple-clock-fixes-v1-1-25f348a5982b@linaro.org>
Quoting Bryan O'Donoghue (2024-03-01 16:52:14)
> It is possible for clk_core_get to dereference a NULL in the following
> sequence:
>
> clk_core_get()
> of_clk_get_hw_from_clkspec()
> __of_clk_get_hw_from_provider()
> __clk_get_hw()
>
> __clk_get_hw() can return NULL which is dereferenced by clk_core_get() at
> hw->core.
>
> Prior to commit dde4eff47c82 ("clk: Look for parents with clkdev based
> clk_lookups") the check IS_ERR_OR_NULL() was performed which would have
> caught the NULL.
>
> Reading the description of this function it talks about returning NULL but
> that cannot be so at the moment.
>
> Update the function to check for hw before dereferencing it and return NULL
> if hw is NULL.
>
> Fixes: dde4eff47c82 ("clk: Look for parents with clkdev based clk_lookups")
> Signed-off-by: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
> ---
I dug through a bunch of old patches and this looks right. I'm not sure
why a provider would ever return NULL though. A NULL pointer means that
the parent is never going to appear so we shouldn't treat this clk as
orphaned in case the clk needs to be clk_get()able and change parents.
This was all part of my plan to introduce a clk_parent_hw() clk op that
returns a pointer and then implement probe defer through clk_get() when
a clk is orphaned. A NULL clk also means a clk is optional and not
there.
Anyway, I've applied this to clk-next. I hope to send out the
clk_parent_hw clk op series soon.
next prev parent reply other threads:[~2024-03-09 0:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-02 0:52 [PATCH 0/2] clk: Fix a core error path and missing qcom camcc-x1e80100 enum Bryan O'Donoghue
2024-03-02 0:52 ` [PATCH 1/2] clk: Fix clk_core_get NULL dereference Bryan O'Donoghue
2024-03-09 0:36 ` Stephen Boyd [this message]
2024-03-02 0:52 ` [PATCH 2/2] clk: qcom: camcc-x1e80100: Fix missing DT_IFACE enum in x1e80100 camcc Bryan O'Donoghue
2024-03-02 1:48 ` Konrad Dybcio
2024-03-03 19:50 ` (subset) [PATCH 0/2] clk: Fix a core error path and missing qcom camcc-x1e80100 enum 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=b809a691de642231b687358eb4bc03aa.sboyd@kernel.org \
--to=sboyd@kernel.org \
--cc=abel.vesa@linaro.org \
--cc=andersson@kernel.org \
--cc=bryan.odonoghue@linaro.org \
--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_rjendra@quicinc.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