From: Matthias Brugger <matthias.bgg@gmail.com>
To: Chenyuan Yang <chenyuan0y@gmail.com>,
geert+renesas@glider.be, linus.walleij@linaro.org,
richardcochran@gmail.com,
angelogioacchino.delregno@collabora.com
Cc: linux-renesas-soc@vger.kernel.org, linux-gpio@vger.kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
zzjas98@gmail.com
Subject: Re: [PATCH] pinctrl: Fix potential NULL pointer dereference
Date: Wed, 12 Feb 2025 09:35:52 +0100 [thread overview]
Message-ID: <6aa1ee3e-8310-450d-9165-7e33cc29f9ca@gmail.com> (raw)
In-Reply-To: <20250210232552.1545887-1-chenyuan0y@gmail.com>
On 11/02/2025 00:25, Chenyuan Yang wrote:
> The `chip.label` could be NULL. Add missing check in the
> rza2_gpio_register().
> This is similar to commit 3027e7b15b02
> ("ice: Fix some null pointer dereference issues in ice_ptp.c").
> Besides, mediatek_gpio_bank_probe() in drivers/gpio/gpio-mt7621.c also
> has a very similar check.
>
> Signed-off-by: Chenyuan Yang <chenyuan0y@gmail.com>
Reviewed-by: Matthias Brugger <matthias.bgg@gmail.com>
> ---
> drivers/pinctrl/renesas/pinctrl-rza2.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/drivers/pinctrl/renesas/pinctrl-rza2.c b/drivers/pinctrl/renesas/pinctrl-rza2.c
> index dd1f8c29d3e7..3da8b0d389c9 100644
> --- a/drivers/pinctrl/renesas/pinctrl-rza2.c
> +++ b/drivers/pinctrl/renesas/pinctrl-rza2.c
> @@ -246,6 +246,9 @@ static int rza2_gpio_register(struct rza2_pinctrl_priv *priv)
> int ret;
>
> chip.label = devm_kasprintf(priv->dev, GFP_KERNEL, "%pOFn", np);
> + if (!chip.label)
> + return -ENOMEM;
> +
> chip.parent = priv->dev;
> chip.ngpio = priv->npins;
>
next prev parent reply other threads:[~2025-02-12 8:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-10 23:25 [PATCH] pinctrl: Fix potential NULL pointer dereference Chenyuan Yang
2025-02-11 7:38 ` Geert Uytterhoeven
2025-02-12 8:35 ` Matthias Brugger [this message]
2025-02-12 12:45 ` Markus Elfring
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=6aa1ee3e-8310-450d-9165-7e33cc29f9ca@gmail.com \
--to=matthias.bgg@gmail.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=chenyuan0y@gmail.com \
--cc=geert+renesas@glider.be \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=richardcochran@gmail.com \
--cc=zzjas98@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;
as well as URLs for NNTP newsgroup(s).