From: Krzysztof Kozlowski <krzk@kernel.org>
To: Joe Hattori <joe@pf.is.s.u-tokyo.ac.jp>,
thierry.reding@gmail.com, jonathanh@nvidia.com
Cc: linux-tegra@vger.kernel.org
Subject: Re: [PATCH] memory: tegra20-emc: fix an OF node reference bug in tegra_emc_find_node_by_ram_code()
Date: Tue, 17 Dec 2024 10:31:23 +0100 [thread overview]
Message-ID: <80e21d04-75a4-4361-8623-0dbadcd4ff2a@kernel.org> (raw)
In-Reply-To: <20241217091434.1993597-1-joe@pf.is.s.u-tokyo.ac.jp>
On 17/12/2024 10:14, Joe Hattori wrote:
> As of_find_node_by_name() release the reference of the given OF node,
No, it does not.
> tegra_emc_find_node_by_ram_code() releases some OF nodes while still in
> use, resulting in possible UAFs. Given the DT structure, utilize the
> for_each_child_of_node macro and of_get_child_by_name() to avoid the bug.
>
> This bug was found by an experimental verification tool that I am
> developing.
>
> Fixes: 96e5da7c8424 ("memory: tegra: Introduce Tegra20 EMC driver")
> Signed-off-by: Joe Hattori <joe@pf.is.s.u-tokyo.ac.jp>
> ---
> drivers/memory/tegra/tegra20-emc.c | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/memory/tegra/tegra20-emc.c b/drivers/memory/tegra/tegra20-emc.c
> index 7193f848d17e..9b7d30a21a5b 100644
> --- a/drivers/memory/tegra/tegra20-emc.c
> +++ b/drivers/memory/tegra/tegra20-emc.c
> @@ -474,14 +474,15 @@ tegra_emc_find_node_by_ram_code(struct tegra_emc *emc)
>
> ram_code = tegra_read_ram_code();
>
> - for (np = of_find_node_by_name(dev->of_node, "emc-tables"); np;
> - np = of_find_node_by_name(np, "emc-tables")) {
> + for_each_child_of_node(dev->of_node, np) {
I don't understand how this change is related to described problem.
> + if (!of_node_name_eq(np, "emc-tables"))
> + continue;
> err = of_property_read_u32(np, "nvidia,ram-code", &value);
> if (err || value != ram_code) {
> struct device_node *lpddr2_np;
> bool cfg_mismatches = false;
>
> - lpddr2_np = of_find_node_by_name(np, "lpddr2");
> + lpddr2_np = of_get_child_by_name(np, "lpddr2");
Why?
> if (lpddr2_np) {
> const struct lpddr2_info *info;
>
> @@ -518,7 +519,6 @@ tegra_emc_find_node_by_ram_code(struct tegra_emc *emc)
> }
>
> if (cfg_mismatches) {
> - of_node_put(np);
If of_find_node_by_name() drops reference, why this was needed?
> continue;
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-12-17 9:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-17 9:14 [PATCH] memory: tegra20-emc: fix an OF node reference bug in tegra_emc_find_node_by_ram_code() Joe Hattori
2024-12-17 9:31 ` Krzysztof Kozlowski [this message]
2024-12-17 11:07 ` Joe Hattori
2024-12-17 11:42 ` Krzysztof Kozlowski
2024-12-17 11:49 ` Dan Carpenter
2024-12-17 11:57 ` Krzysztof Kozlowski
2024-12-18 2:48 ` Joe Hattori
2024-12-22 10:08 ` Krzysztof Kozlowski
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=80e21d04-75a4-4361-8623-0dbadcd4ff2a@kernel.org \
--to=krzk@kernel.org \
--cc=joe@pf.is.s.u-tokyo.ac.jp \
--cc=jonathanh@nvidia.com \
--cc=linux-tegra@vger.kernel.org \
--cc=thierry.reding@gmail.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