From: Vinod Koul <vkoul@kernel.org>
To: sven@kernel.org, j@jannau.net, neal@gompa.dev,
neil.armstrong@linaro.org, marcan@marcan.st,
p.zabel@pengutronix.de, David Carlier <devnexen@gmail.com>
Cc: olteanv@gmail.com, asahi@lists.linux.dev,
linux-arm-kernel@lists.infradead.org,
linux-phy@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] phy: apple: atc: Fix typec switch/mux leak on unbind
Date: Thu, 14 May 2026 21:38:19 +0530 [thread overview]
Message-ID: <177877489977.1079578.13272721889190867698.b4-ty@kernel.org> (raw)
In-Reply-To: <20260508201958.30060-1-devnexen@gmail.com>
On Fri, 08 May 2026 21:19:58 +0100, David Carlier wrote:
> atcphy_probe_switch() and atcphy_probe_mux() discard the pointers
> returned by typec_switch_register() and typec_mux_register(). The
> platform driver has no .remove callback, so when the driver unbinds
> (e.g. via sysfs unbind) neither typec_switch_unregister() nor
> typec_mux_unregister() is called. The framework reference taken in
> typec_switch_register() (device_initialize() + device_add() in
> drivers/usb/typec/mux.c) is therefore never dropped and the
> typec_switch_dev / typec_mux_dev objects stay live forever, with
> their sysfs entries under the typec_mux class also left behind. A
> subsequent rebind cannot recreate them with the same fwnode-derived
> name.
>
> [...]
Applied, thanks!
[1/1] phy: apple: atc: Fix typec switch/mux leak on unbind
commit: 1854082fe0ddb81bc93d1f8e8a00554217fd09d1
Best regards,
--
~Vinod
--
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy
prev parent reply other threads:[~2026-05-14 16:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-07 16:37 [PATCH v2] phy: apple: atc: Fix typec switch/mux leak on unbind David Carlier
2026-05-08 20:01 ` Vladimir Oltean
2026-05-08 20:19 ` [PATCH v3] " David Carlier
2026-05-08 23:06 ` Joshua Peisach
2026-05-14 16:08 ` Vinod Koul [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=177877489977.1079578.13272721889190867698.b4-ty@kernel.org \
--to=vkoul@kernel.org \
--cc=asahi@lists.linux.dev \
--cc=devnexen@gmail.com \
--cc=j@jannau.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=marcan@marcan.st \
--cc=neal@gompa.dev \
--cc=neil.armstrong@linaro.org \
--cc=olteanv@gmail.com \
--cc=p.zabel@pengutronix.de \
--cc=sven@kernel.org \
/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