From: Heikki Krogerus <heikki.krogerus@linux.intel.com>
To: Wentao Liang <vulab@iscas.ac.cn>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-usb@vger.kernel.org
Subject: Re: [PATCH] usb: typec: thunderbolt: release a non-Thunderbolt cable plug
Date: Fri, 6 Nov 2026 18:42:29 +0100 [thread overview]
Message-ID: <au4RhYRvP2s8Rzoa@black.igk.intel.com> (raw)
In-Reply-To: <20261104021516.1468625-1-vulab@iscas.ac.cn>
On Wed, Nov 04, 2026 at 02:15:16AM +0000, Wentao Liang wrote:
> tbt_ready() takes a reference on each cable plug with
> typec_altmode_get_plug() and keeps it in tbt->plug[] for the lifetime of
> the alternate mode. When a plug reports an SVID other than Thunderbolt,
> the loop breaks without storing the plug, so the reference taken for it
> is never dropped.
>
> Put that plug before leaving the loop on the SVID mismatch path.
>
> Fixes: 100e25738659 ("usb: typec: Add driver for Thunderbolt 3 Alternate Mode")
> Cc: stable@vger.kernel.org
> Assisted-by: DeepSeek-V4.1-Flash and OpenAI Codex
> Signed-off-by: Wentao Liang <vulab@iscas.ac.cn>
Reviewed-by: Heikki Krogerus <heikki.krogerus@linux.intel.com>
> ---
> drivers/usb/typec/altmodes/thunderbolt.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/usb/typec/altmodes/thunderbolt.c b/drivers/usb/typec/altmodes/thunderbolt.c
> index 2e1b1a1da7d9..fad48aae6751 100644
> --- a/drivers/usb/typec/altmodes/thunderbolt.c
> +++ b/drivers/usb/typec/altmodes/thunderbolt.c
> @@ -340,8 +340,10 @@ static bool tbt_ready(struct typec_altmode *alt)
> if (!plug)
> continue;
>
> - if (plug->svid != USB_TYPEC_TBT_SID)
> + if (plug->svid != USB_TYPEC_TBT_SID) {
> + typec_altmode_put_plug(plug);
> break;
> + }
>
> plug->desc = "Thunderbolt3";
> plug->cable_ops = &tbt_cable_ops;
> --
> 2.34.1
>
--
heikki
prev parent reply other threads:[~2026-11-06 17:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-04 2:15 [PATCH] usb: typec: thunderbolt: release a non-Thunderbolt cable plug Wentao Liang
2026-11-04 2:26 ` sashiko-bot
2026-11-06 17:42 ` Heikki Krogerus [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=au4RhYRvP2s8Rzoa@black.igk.intel.com \
--to=heikki.krogerus@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-usb@vger.kernel.org \
--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