From: Vladimir Oltean <olteanv@gmail.com>
To: Ma Ke <make24@iscas.ac.cn>
Cc: woojung.huh@microchip.com, UNGLinuxDriver@microchip.com,
andrew@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, o.rempel@pengutronix.de,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
akpm@linux-foundation.org, stable@vger.kernel.org
Subject: Re: [PATCH] net: dsa: microchip: fix mdio parent bus reference leak
Date: Sun, 23 Nov 2025 13:36:43 +0200 [thread overview]
Message-ID: <20251123113643.cf2kc7i5cvdkkaf2@skbuf> (raw)
In-Reply-To: <20251121042000.20119-1-make24@iscas.ac.cn>
On Fri, Nov 21, 2025 at 12:20:00PM +0800, Ma Ke wrote:
> In ksz_mdio_register(), when of_mdio_find_bus() is called to get the
> parent MDIO bus, it increments the reference count of the underlying
> device. However, the reference are not released in error paths or
> during switch teardown, causing a reference leak.
>
> Add put_device() in the error path of ksz_mdio_register() and
> ksz_teardown() to release the parent bus.
>
> Found by code review.
>
> Cc: stable@vger.kernel.org
> Fixes: 9afaf0eec2ab ("net: dsa: microchip: Refactor MDIO handling for side MDIO access")
> Signed-off-by: Ma Ke <make24@iscas.ac.cn>
> ---
> drivers/net/dsa/microchip/ksz_common.c | 10 ++++++++++
> 1 file changed, 10 insertions(+)
>
> diff --git a/drivers/net/dsa/microchip/ksz_common.c b/drivers/net/dsa/microchip/ksz_common.c
> index 933ae8dc6337..49c0420a6df8 100644
> --- a/drivers/net/dsa/microchip/ksz_common.c
> +++ b/drivers/net/dsa/microchip/ksz_common.c
> @@ -2795,6 +2795,11 @@ static int ksz_mdio_register(struct ksz_device *dev)
> }
>
> put_mdio_node:
> + if (ret && dev->parent_mdio_bus) {
> + put_device(&dev->parent_mdio_bus->dev);
> + dev->parent_mdio_bus = NULL;
> + }
> +
> of_node_put(mdio_np);
> of_node_put(parent_bus_node);
>
> @@ -3110,6 +3115,11 @@ static void ksz_teardown(struct dsa_switch *ds)
> ksz_irq_free(&dev->girq);
> }
>
> + if (dev->parent_mdio_bus) {
> + put_device(&dev->parent_mdio_bus->dev);
> + dev->parent_mdio_bus = NULL;
> + }
> +
> if (dev->dev_ops->teardown)
> dev->dev_ops->teardown(ds);
> }
> --
> 2.17.1
>
Thank you for the patch.
I see 2 problems:
1. I'm not sure that releasing the reference to the parent_mdio_bus
device is compatible with devres, since the MDIO bus created by
ksz_mdio_register() will continue to exist after we release the
parent_mdio_bus reference. I think it would be better to remove
devres, introduce ksz_mdio_unregister(), and only release the
reference once our MDIO bus is unregistered.
2. Error path handling is incomplete:
ret = ksz_mdio_register(dev);
if (ret < 0) {
dev_err(dev->dev, "failed to register the mdio");
goto out_ptp_clock_unregister;
}
ret = ksz_dcb_init(dev);
if (ret)
goto out_ptp_clock_unregister; // needs to call ksz_mdio_unregister()
prev parent reply other threads:[~2025-11-23 11:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-21 4:20 [PATCH] net: dsa: microchip: fix mdio parent bus reference leak Ma Ke
2025-11-21 5:41 ` Oleksij Rempel
2025-11-23 11:36 ` Vladimir Oltean [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=20251123113643.cf2kc7i5cvdkkaf2@skbuf \
--to=olteanv@gmail.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=akpm@linux-foundation.org \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=make24@iscas.ac.cn \
--cc=netdev@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
--cc=pabeni@redhat.com \
--cc=stable@vger.kernel.org \
--cc=woojung.huh@microchip.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