public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: "Kaustabh Chakraborty" <kauschluss@disroot.org>
To: "chiffathefox" <chiffathefoxx@gmail.com>, "Marek Vasut" <marex@denx.de>
Cc: "Kaustabh Chakraborty" <kauschluss@disroot.org>,
	"Lukasz Majewski" <lukma@denx.de>,
	"Minkyu Kang" <mk7.kang@samsung.com>,
	"Sam Protsenko" <semen.protsenko@linaro.org>,
	"Tom Rini" <trini@konsulko.com>, <u-boot@lists.denx.de>
Subject: Re: [PATCH 2/2] clk: exynos: do not reparent requested clock
Date: Mon, 19 Jan 2026 22:30:24 +0530	[thread overview]
Message-ID: <DFSQ602NFWQ7.25DB4BQ6SHEHC@disroot.org> (raw)
In-Reply-To: <20260115031114.220888-3-chiffathefoxx@gmail.com>

On 2026-01-15 05:11 +02:00, chiffathefox wrote:
> It would appear the original developer of this driver
> reparented child clock devices to fix the issue described in
> `clk: clk_resolve_parent_clk(): resolve external clocks by id`.
> This hacky fix was the cause of invalid memory access when calling
> clk_get_rate() on a clock retrieved via clk_get_by_index().
> clk_get_by_index() returns a copy of the `struct clk` and
> when passed to clk_get_rate() it may be forwarded to
> clk_divider_recalc_rate(), which will cause the latter to
> run container_of() on a pointer from caller's stack instead
> of the pointer that was kzalloc()'d by the clk-divider driver.
>
> Signed-off-by: chiffathefox <chiffathefoxx@gmail.com>

Tested-by: Kaustabh Chakraborty <kauschluss@disroot.org> # exynos-mobile/exynos7870

      reply	other threads:[~2026-01-19 17:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-15  3:11 [PATCH 0/2] Improvements to the recent clock rework by marex chiffathefox
2026-01-15  3:11 ` [PATCH 1/2] clk: clk_resolve_parent_clk(): resolve external clocks by id chiffathefox
2026-01-17  1:38   ` Marek Vasut
2026-01-19 16:59   ` Kaustabh Chakraborty
2026-01-15  3:11 ` [PATCH 2/2] clk: exynos: do not reparent requested clock chiffathefox
2026-01-19 17:00   ` Kaustabh Chakraborty [this message]

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=DFSQ602NFWQ7.25DB4BQ6SHEHC@disroot.org \
    --to=kauschluss@disroot.org \
    --cc=chiffathefoxx@gmail.com \
    --cc=lukma@denx.de \
    --cc=marex@denx.de \
    --cc=mk7.kang@samsung.com \
    --cc=semen.protsenko@linaro.org \
    --cc=trini@konsulko.com \
    --cc=u-boot@lists.denx.de \
    /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