From: Myeonghun Pak <mhun512@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Thierry Reding <thierry.reding@kernel.org>,
Jonathan Hunter <jonathanh@nvidia.com>
Cc: linux-usb@vger.kernel.org, linux-tegra@vger.kernel.org,
linux-kernel@vger.kernel.org, Ijae Kim <ae878000@gmail.com>,
stable@vger.kernel.org
Subject: [PATCH v2 0/2] usb: gadget: tegra-xudc: Fix removal-time work races
Date: Mon, 21 Sep 2026 19:08:46 -0400 [thread overview]
Message-ID: <20260921230849.502492-1-mhun512@gmail.com> (raw)
Two producers outlive tegra_xudc_remove(), from different commits.
Only the delayed-work fix needs an API added in v6.10.
The devm port-status IRQ queues port_reset_war_work and plc_reset_work.
disable_delayed_work_sync() rejects a later queue.
The PHY notifier queues usb_role_sw_work and is not devres-managed.
Unregister it, then keep cancel_work_sync(). That applies below v6.10.
Changes in v2:
- Split the Fixes tags. Only patch 2/2 is marked # 6.10+.
- Keep each Fixes tag on one line. (Thierry Reding)
- Disable plc_reset_work too. The port-status IRQ can requeue it.
(Thierry Reding)
- Unregister the VBUS notifier before draining usb_role_sw_work.
Myeonghun Pak (2):
usb: gadget: tegra-xudc: Unregister VBUS notifier
usb: gadget: tegra-xudc: Disable reset delayed works
drivers/usb/gadget/udc/tegra-xudc.c | 9 ++++++++-
1 file changed, 8 insertions(+), 1 deletion(-)
base-commit: 238650ef6c7c7cca08e032527329424c9fbd70e5
--
2.53.0
next reply other threads:[~2026-09-21 23:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-21 23:08 Myeonghun Pak [this message]
2026-09-21 23:08 ` [PATCH v2 1/2] usb: gadget: tegra-xudc: Unregister VBUS notifier Myeonghun Pak
2026-09-21 23:08 ` [PATCH v2 2/2] usb: gadget: tegra-xudc: Disable reset delayed works Myeonghun Pak
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=20260921230849.502492-1-mhun512@gmail.com \
--to=mhun512@gmail.com \
--cc=ae878000@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=thierry.reding@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
all inboxes | Powered by JetHome®