From: patchwork-bot+netdevbpf@kernel•org
To: ALOK TIWARI <alok.a.tiwari@oracle•com>
Cc: ansuelsmth@gmail•com, hkallweit1@gmail•com, andrew@lunn•ch,
kuba@kernel•org, davem@davemloft•net, edumazet@google•com,
pabeni@redhat•com, horms@kernel•org, netdev@vger•kernel.org,
alok.a.tiwarilinux@gmail•com
Subject: Re: [PATCH net] net: mdio: Check regmap pointer returned by device_node_to_regmap()
Date: Tue, 04 Nov 2025 01:10:19 +0000 [thread overview]
Message-ID: <176221861900.2276313.11074104709182763638.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251031161607.58581-1-alok.a.tiwari@oracle.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel•org>:
On Fri, 31 Oct 2025 09:15:53 -0700 you wrote:
> The call to device_node_to_regmap() in airoha_mdio_probe() can return
> an ERR_PTR() if regmap initialization fails. Currently, the driver
> stores the pointer without validation, which could lead to a crash
> if it is later dereferenced.
>
> Add an IS_ERR() check and return the corresponding error code to make
> the probe path more robust.
>
> [...]
Here is the summary with links:
- [net] net: mdio: Check regmap pointer returned by device_node_to_regmap()
https://git.kernel.org/netdev/net/c/b2b526c2cf57
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2025-11-04 1:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-31 16:15 [PATCH net] net: mdio: Check regmap pointer returned by device_node_to_regmap() Alok Tiwari
2025-10-31 16:32 ` Andrew Lunn
2025-11-04 1:10 ` patchwork-bot+netdevbpf [this message]
2025-11-04 12:01 ` Christian Marangi
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=176221861900.2276313.11074104709182763638.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel$(echo .)org \
--cc=alok.a.tiwari@oracle$(echo .)com \
--cc=alok.a.tiwarilinux@gmail$(echo .)com \
--cc=andrew@lunn$(echo .)ch \
--cc=ansuelsmth@gmail$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=edumazet@google$(echo .)com \
--cc=hkallweit1@gmail$(echo .)com \
--cc=horms@kernel$(echo .)org \
--cc=kuba@kernel$(echo .)org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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