mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: <kojima.masahisa@socionext.com>
To: <yigejiang86@gmail.com>, <netdev@vger.kernel.org>
Cc: <ilias.apalodimas@linaro.org>, <andrew+netdev@lunn.ch>,
	<davem@davemloft.net>, <edumazet@google.com>, <kuba@kernel.org>,
	<pabeni@redhat.com>, <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH net-next] net: netsec: fix device_node reference leak on phy_np
Date: Wed, 16 Sep 2026 02:28:37 +0000	[thread overview]
Message-ID: <TYYP286MB0924762C90163A2A847D72CEE3B92@TYYP286MB0924.JPNP286.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <20260913064102.37452-1-yigejiang86@gmail.com>

> netsec_of_probe() takes a reference on the PHY device_node with
> of_parse_phandle() and stores it in priv->phy_np, but the driver never
> drops it.  One device_node reference is leaked per probe, on the success
> path as well as on every error path reached after netsec_of_probe().
> 
> Neither consumer takes ownership.  of_mdio_parse_addr() is a static
> inline taking a const struct device_node * that only reads the "reg"
> property.  of_phy_connect() borrows as well: of_phy_get_and_connect() in
> drivers/net/mdio/of_mdio.c brackets its own call with of_node_get() at
> :364 and of_node_put() at :373, which would be a double put if
> of_phy_connect() consumed the reference.
> 
> The node is still in use at netsec_netdev_open() time, where it is
> passed to of_phy_connect(), so it has device lifetime.  Release it at
> the probe error label, which every failure path after the acquire
> funnels through, and in netsec_remove().  Both releases precede
> free_netdev(), since priv is netdev_priv(ndev).  The ACPI probe path
> leaves priv->phy_np NULL and of_node_put(NULL) is a no-op.
> 
> There is no end-user visible symptom on currently supported platforms:
> a device_node is only freed once OF_DYNAMIC is enabled and the node has
> been detached, so on a static device tree the imbalance is inert.  It is
> observable as a refcount that grows across bind/unbind cycles, and would
> matter under device tree overlays.
> 
> Found by static analysis of reference acquire/release pairing rather
> than from a runtime report.  No reproducer was produced and the change
> has not been runtime tested; it is compile-tested only (arm64,
> CONFIG_SNI_NETSEC=m via COMPILE_TEST).

Tested on SynQuacer.
Verified repeated load/unload cycles and network connectivity.

Tested-by: Masahisa Kojima <kojima.masahisa@socionext.com>

> 
> Fixes: 533dd11a12f6 ("net: socionext: Add Synquacer NetSec driver")
> Assisted-by: LLM
> Signed-off-by: Yige Jiang <yigejiang86@gmail.com>
> ---
>  drivers/net/ethernet/socionext/netsec.c | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/drivers/net/ethernet/socionext/netsec.c
> b/drivers/net/ethernet/socionext/netsec.c
> index d14a6584473c8..79a0a324c921d 100644
> --- a/drivers/net/ethernet/socionext/netsec.c
> +++ b/drivers/net/ethernet/socionext/netsec.c
> @@ -2149,6 +2149,7 @@ static int netsec_probe(struct platform_device
> *pdev)
>  	pm_runtime_put_sync(&pdev->dev);
>  	pm_runtime_disable(&pdev->dev);
>  free_ndev:
> +	of_node_put(priv->phy_np);
>  	free_netdev(ndev);
>  	dev_err(&pdev->dev, "init failed\n");
> 
> @@ -2166,6 +2167,7 @@ static void netsec_remove(struct platform_device
> *pdev)
>  	netif_napi_del(&priv->napi);
> 
>  	pm_runtime_disable(&pdev->dev);
> +	of_node_put(priv->phy_np);
>  	free_netdev(priv->ndev);
>  }
> 
> --
> 2.50.1 (Apple Git-155)





  parent reply	other threads:[~2026-09-16  2:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-13  6:41 Yige Jiang
2026-09-14 10:41 ` Simon Horman
2026-09-16  2:28 ` kojima.masahisa [this message]
2026-09-17  0:40 ` patchwork-bot+netdevbpf

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=TYYP286MB0924762C90163A2A847D72CEE3B92@TYYP286MB0924.JPNP286.PROD.OUTLOOK.COM \
    --to=kojima.masahisa@socionext.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=ilias.apalodimas@linaro.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=yigejiang86@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®