From: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
To: Fan Wu <fanwu01@zju.edu.cn>, linux-usb@vger.kernel.org
Cc: heikki.krogerus@linux.intel.com, gregkh@linuxfoundation.org,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH] usb: typec: qcom-pmic-typec: disable cc_debounce_dwork on stop
Date: Thu, 20 Aug 2026 11:18:31 +0100 [thread overview]
Message-ID: <3662ce56-7471-491f-b2db-7a87a4379099@linaro.org> (raw)
In-Reply-To: <20260819161950.77858-1-fanwu01@zju.edu.cn>
On 19/08/2026 17:19, Fan Wu wrote:
> cc_debounce_dwork lives on the system workqueue but is armed from
> tcpm callbacks (set_cc/start_toggling). Those callbacks run on tcpm's
> kthread worker which is only destroyed by tcpm_unregister_port(), after
> port_stop() has already returned, opening a potential race window where
> tcpm's worker flush re-arms the work.
>
> Use disable_delayed_work_sync() in port_stop() to cancel any pending
> instance and prevent future schedule_delayed_work() calls from
> succeeding. Also unwind a failed port_start() through port_stop(),
> which otherwise jumps straight to tcpm_unregister_port() and leaves
> the same window open after a failed probe.
I'd prefer to see two patches broken at the "also" in the above statement.
>
> This issue was found by an in-house static analysis tool.
>
> Fixes: a4422ff22142 ("usb: typec: qcom: Add Qualcomm PMIC Type-C driver")
> Cc: stable@vger.kernel.org # v6.10+
> Assisted-by: Codex:gpt-5.6
> Signed-off-by: Fan Wu <fanwu01@zju.edu.cn>
> ---
> drivers/usb/typec/tcpm/qcom/qcom_pmic_typec.c | 3 +--
> drivers/usb/typec/tcpm/qcom/qcom_pmic_typec_port.c | 2 ++
> 2 files changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/usb/typec/tcpm/qcom/qcom_pmic_typec.c b/drivers/usb/typec/tcpm/qcom/qcom_pmic_typec.c
> index 35320f89d..f42c9e65f 100644
> --- a/drivers/usb/typec/tcpm/qcom/qcom_pmic_typec.c
> +++ b/drivers/usb/typec/tcpm/qcom/qcom_pmic_typec.c
> @@ -101,7 +101,7 @@ static int qcom_pmic_typec_probe(struct platform_device *pdev)
>
> ret = tcpm->port_start(tcpm, tcpm->tcpm_port);
> if (ret)
> - goto port_unregister;
> + goto port_stop;
>
> ret = tcpm->pdphy_start(tcpm, tcpm->tcpm_port);
> if (ret)
> @@ -117,7 +117,6 @@ static int qcom_pmic_typec_probe(struct platform_device *pdev)
> tcpm->pdphy_stop(tcpm);
> port_stop:
> tcpm->port_stop(tcpm);
> -port_unregister:
> tcpm_unregister_port(tcpm->tcpm_port);
> fwnode_remove:
> fwnode_handle_put(tcpm->tcpc.fwnode);
> diff --git a/drivers/usb/typec/tcpm/qcom/qcom_pmic_typec_port.c b/drivers/usb/typec/tcpm/qcom/qcom_pmic_typec_port.c
> index 429bd42a0..fdc379fc4 100644
> --- a/drivers/usb/typec/tcpm/qcom/qcom_pmic_typec_port.c
> +++ b/drivers/usb/typec/tcpm/qcom/qcom_pmic_typec_port.c
> @@ -694,6 +694,8 @@ static void qcom_pmic_typec_port_stop(struct pmic_typec *tcpm)
>
> for (i = 0; i < pmic_typec_port->nr_irqs; i++)
> disable_irq(pmic_typec_port->irq_data[i].irq);
> +
> + disable_delayed_work_sync(&pmic_typec_port->cc_debounce_dwork);
> }
>
> int qcom_pmic_typec_port_probe(struct platform_device *pdev,
>
next prev parent reply other threads:[~2026-08-20 10:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-19 16:19 [PATCH] usb: typec: qcom-pmic-typec: disable cc_debounce_dwork on stop Fan Wu
2026-08-20 8:13 ` Konrad Dybcio
2026-08-20 8:52 ` Fan Wu
2026-08-20 10:18 ` Bryan O'Donoghue [this message]
2026-08-20 13:53 ` [PATCH v2 0/2] usb: typec: qcom-pmic-typec: cc_debounce_dwork lifetime fixes Fan Wu
2026-08-20 13:53 ` [PATCH v2 1/2] usb: typec: qcom-pmic-typec: disable cc_debounce_dwork on stop Fan Wu
2026-08-31 9:56 ` Heikki Krogerus
2026-08-20 13:53 ` [PATCH v2 2/2] usb: typec: qcom-pmic-typec: drain cc_debounce_dwork if port_start() fails Fan Wu
2026-08-31 9:57 ` Heikki Krogerus
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=3662ce56-7471-491f-b2db-7a87a4379099@linaro.org \
--to=bryan.odonoghue@linaro.org \
--cc=fanwu01@zju.edu.cn \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=stable@vger.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