From: Simon Horman <horms@kernel.org>
To: Wentao Liang <vulab@iscas.ac.cn>
Cc: alexandre.torgue@foss.st.com, andrew+netdev@lunn.ch,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
mcoquelin.stm32@gmail.com, netdev@vger.kernel.org,
pabeni@redhat.com, treding@nvidia.com, stable@vger.kernel.org
Subject: Re: [PATCH] net: stmmac: Fix MDIO node leak in stmmac_mdio_setup()
Date: Mon, 21 Sep 2026 13:11:20 +0100 [thread overview]
Message-ID: <20260921121120.GK13925@horms.kernel.org> (raw)
In-Reply-To: <20260917113945.2149361-1-vulab@iscas.ac.cn>
On Thu, Sep 17, 2026 at 11:39:45AM +0000, Wentao Liang wrote:
> stmmac_mdio_setup() acquires a reference on the MDIO node through
> stmmac_of_get_mdio() and stores it in plat->mdio_node. If the allocation
> of plat->mdio_bus_data fails, the function returns -ENOMEM and the
> caller takes the error_put_phy path, which only releases plat->phy_node,
> so the MDIO node reference is leaked.
>
> Release plat->mdio_node on this error path.
>
> Fixes: 1a981c0586c0 ("net: stmmac: Make MDIO bus reset optional")
> Cc: stable@vger.kernel.org
> Signed-off-by: Wentao Liang <vulab@iscas.ac.cn>
> ---
> drivers/net/ethernet/stmicro/stmmac/stmmac_platform.c | 5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/net/ethernet/stmicro/stmmac/stmmac_platform.c b/drivers/net/ethernet/stmicro/stmmac/stmmac_platform.c
> index 5cae2aa72906..09359ccb32ef 100644
> --- a/drivers/net/ethernet/stmicro/stmmac/stmmac_platform.c
> +++ b/drivers/net/ethernet/stmicro/stmmac/stmmac_platform.c
> @@ -356,8 +356,11 @@ static int stmmac_mdio_setup(struct plat_stmmacenet_data *plat,
> plat->mdio_bus_data = devm_kzalloc(dev,
> sizeof(*plat->mdio_bus_data),
> GFP_KERNEL);
> - if (!plat->mdio_bus_data)
> + if (!plat->mdio_bus_data) {
> + of_node_put(plat->mdio_node);
> + plat->mdio_node = NULL;
> return -ENOMEM;
> + }
>
> plat->mdio_bus_data->needs_reset = true;
> }
Hi Wentao,
As per my comment on another one of your recent patches, I think this
change would be somewhat more robust against future changes to this
function if it was implemented using a goto-driven unwind ladder, which is
the generally preferred in Networking code.
Something like this (compile tested only!):
diff --git a/drivers/net/ethernet/stmicro/stmmac/stmmac_platform.c b/drivers/net/ethernet/stmicro/stmmac/stmmac_platform.c
index 3ea16d618215..ded352afd103 100644
--- a/drivers/net/ethernet/stmicro/stmmac/stmmac_platform.c
+++ b/drivers/net/ethernet/stmicro/stmmac/stmmac_platform.c
@@ -356,12 +356,17 @@ static int stmmac_mdio_setup(struct plat_stmmacenet_data *plat,
sizeof(*plat->mdio_bus_data),
GFP_KERNEL);
if (!plat->mdio_bus_data)
- return -ENOMEM;
+ goto err_put_mdio_node;
plat->mdio_bus_data->needs_reset = true;
}
return 0;
+
+err_put_mdio_node:
+ of_node_put(plat->mdio_node);
+ plat->mdio_node = NULL;
+ return -ENOMEM;
}
/**
--
pw-bot: changes-requested
prev parent reply other threads:[~2026-09-21 12:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-17 11:39 Wentao Liang
2026-09-21 12:11 ` Simon Horman [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=20260921121120.GK13925@horms.kernel.org \
--to=horms@kernel.org \
--cc=alexandre.torgue@foss.st.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=stable@vger.kernel.org \
--cc=treding@nvidia.com \
--cc=vulab@iscas.ac.cn \
/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®