From: Xianwei Zhao <xianwei.zhao@amlogic.com>
To: Felix Gu <ustc.gu@gmail.com>, Linus Walleij <linusw@kernel.org>,
Neil Armstrong <neil.armstrong@linaro.org>,
Kevin Hilman <khilman@baylibre.com>,
Jerome Brunet <jbrunet@baylibre.com>,
Martin Blumenstingl <martin.blumenstingl@googlemail.com>
Cc: linux-amlogic@lists.infradead.org, linux-gpio@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] pinctrl: meson: amlogic-a4: Fix device node reference leak in bank helpers
Date: Wed, 28 Jan 2026 10:37:25 +0800 [thread overview]
Message-ID: <5e95f52c-92d3-426a-b91c-22bdf42dd65c@amlogic.com> (raw)
In-Reply-To: <20260128-amlogic-v1-1-c8aeb2953dcf@gmail.com>
Reviewed-by: Xianwei Zhao <xianwei.zhao@amlogic.com>
On 2026/1/28 02:23, Felix Gu wrote:
> [You don't often get email from ustc.gu@gmail.com. Learn why this is important at https://aka.ms/LearnAboutSenderIdentification ]
>
> [ EXTERNAL EMAIL ]
>
> of_parse_phandle_with_fixed_args() increments the reference count of the
> returned device node, so it must be explicitly released using
> of_node_put() after use.
>
> Fix the reference leak in aml_bank_pins() and aml_bank_number() by
> adding the missing of_node_put() calls.
>
> Fixes: 6e9be3abb78c ("pinctrl: Add driver support for Amlogic SoCs")
> Signed-off-by: Felix Gu <ustc.gu@gmail.com>
> ---
> drivers/pinctrl/meson/pinctrl-amlogic-a4.c | 10 ++++++----
> 1 file changed, 6 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/pinctrl/meson/pinctrl-amlogic-a4.c b/drivers/pinctrl/meson/pinctrl-amlogic-a4.c
> index ded7b218e2ec..40542edd557e 100644
> --- a/drivers/pinctrl/meson/pinctrl-amlogic-a4.c
> +++ b/drivers/pinctrl/meson/pinctrl-amlogic-a4.c
> @@ -725,8 +725,9 @@ static u32 aml_bank_pins(struct device_node *np)
> if (of_parse_phandle_with_fixed_args(np, "gpio-ranges", 3,
> 0, &of_args))
> return 0;
> - else
> - return of_args.args[2];
> +
> + of_node_put(of_args.np);
> + return of_args.args[2];
> }
>
> static int aml_bank_number(struct device_node *np)
> @@ -736,8 +737,9 @@ static int aml_bank_number(struct device_node *np)
> if (of_parse_phandle_with_fixed_args(np, "gpio-ranges", 3,
> 0, &of_args))
> return -EINVAL;
> - else
> - return of_args.args[1] >> 8;
> +
> + of_node_put(of_args.np);
> + return of_args.args[1] >> 8;
> }
>
> static unsigned int aml_count_pins(struct device_node *np)
>
> ---
> base-commit: 615aad0f61e0c7a898184a394dc895c610100d4f
> change-id: 20260128-amlogic-0d08ef086c8b
>
> Best regards,
> --
> Felix Gu <ustc.gu@gmail.com>
>
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
next prev parent reply other threads:[~2026-01-28 2:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-27 18:23 Felix Gu
2026-01-28 2:37 ` Xianwei Zhao [this message]
2026-02-03 0:29 ` Linus Walleij
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=5e95f52c-92d3-426a-b91c-22bdf42dd65c@amlogic.com \
--to=xianwei.zhao@amlogic.com \
--cc=jbrunet@baylibre.com \
--cc=khilman@baylibre.com \
--cc=linusw@kernel.org \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.blumenstingl@googlemail.com \
--cc=neil.armstrong@linaro.org \
--cc=ustc.gu@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
all inboxes | Powered by JetHome®