From: Mario Limonciello <superm1@kernel.org>
To: Sanath.S@amd.com, "Natikar,
Basavaraj" <basavaraj.natikar@amd.com>,
Juan Martinez <Juan.Martinez@amd.com>
Cc: westeri@kernel.org, andreas.noever@gmail.com,
YehezkelShB@gmail.com, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org,
Mika Westerberg <mika.westerberg@linux.intel.com>
Subject: Re: [PATCH v5] thunderbolt: Fix tb->lock deadlock during hot-unplug on AMD USB4 routers
Date: Wed, 9 Sep 2026 14:06:06 -0500 [thread overview]
Message-ID: <21cbfbaf-ef1f-469b-a33b-8d623dd7f9a3@kernel.org> (raw)
In-Reply-To: <20260902054800.GI106095@black.igk.intel.com>
On 9/2/26 00:48, Mika Westerberg wrote:
> Hi,
>
> On Tue, Sep 01, 2026 at 05:16:03PM -0500, Mario Limonciello wrote:
>> On 8/31/26 11:16, juan.martinez@amd.com wrote:
>>> From: Juan Martinez <juan.martinez@amd.com>
>>>
>>> Commit f1de1fc5f632 ("thunderbolt: Add quirk to reset host interface on
>>> DMA path teardown for AMD USB4 routers") introduced a deadlock when
>>> physically unplugging a Thunderbolt cable on AMD systems.
>>>
>>> The problem occurs because tb_handle_hotplug() holds tb->lock while
>>> processing the unplug event. When it removes the XDomain services,
>>> tbnet_remove() calls tb_xdomain_disable_paths() which eventually calls
>>> tb_domain_reset_interface(). That function tries to acquire tb->lock
>>> via guard(mutex), but the hotplug worker already holds it, causing a
>>> self-deadlock.
>>>
>>> The deadlock manifests as a complete network hang because
>>> tb_handle_hotplug() holds RTNL while waiting on its own mutex, blocking
>>> all network operations system-wide.
>>>
>>> The existing code already handles this scenario partially: when
>>> xd->is_unplugged is true, tb_disconnect_xdomain_paths() intentionally
>>> skips the DMA teardown because the hotplug handler tears down the DMA
>>> tunnels itself. However, the reset was still being called
>>> unconditionally.
>>>
>>> Fix this by splitting tb_domain_reset_interface() into a locked inner
>>> function and a locking wrapper. Skip the reset from
>>> tb_domain_disconnect_xdomain_paths() when xd->is_unplugged is true, and
>>> instead reset the interface after the hotplug handler tears down the DMA
>>> tunnel while already holding tb->lock.
>>>
>>> Handle both unplug topologies: reset after the direct XDomain teardown,
>>> and after invalid DMA tunnels are removed when an upstream router and its
>>> downstream XDomain are unplugged together.
>>>
>>> This preserves the reset behavior for normal shutdown paths while
>>> avoiding the deadlock during physical cable unplug.
>>>
>>> Fixes: f1de1fc5f632 ("thunderbolt: Add quirk to reset host interface on DMA path teardown for AMD USB4 routers")
>>> Signed-off-by: Juan Martinez <juan.martinez@amd.com>
>>
>> Reviewed-by: Mario Limonciello (AMD) <superm1@kernel.org>
>>
>> BTW -
>>
>> I did take a look through the Sashiko feedback and the first point doesn't
>> matter because no pre-USB4 hosts take this quirk.
>>
>> The second point is a side effect of this reset and accepted behavior.
>
> I did not find Sashiko comments for this last version but started thinking
> that the way we are doing it now is quite brutal. Say we have this setup:
>
> - Thunderbolt networking for control traffic
> - One USB4STREAM for data plane
>
> The data plane comes and goes depending on the needs but what happens now
> is that after USB4STREAM tears down the tunnels, the whole host interface
> get reset so that makes the Thunderbolt networking to fail as well.
>
> Is the original hardware hang per-ring? So for example in this case without
> any fixes the rings for USB4STREAM would hang but the Thunderbolt
> networking would keep working? I would expect so bot it would be good to
> confirm.
>
> Because then I think what we can do is to revert the original fix and then
> handle this all in nhi.c so that we delay the reset until the rings are
> idle and during that time we hand off "unused" rings (until running out of
> them). After we find the rings to be idle we block the CM and control
> channel and do the reset. I don't know how many rings AMD hardware has,
> though.
>
IIUC the problem ends up happening while tearing down xdomain. So if a
few xdomain tunnels are active you can hit it.
Juan, Sanath, Basavaraj, can you please check and comment?
> I sketched something along those lines (only compile tested) with LLM see
> below. I wonder if this could work?
>
> diff --git a/drivers/thunderbolt/domain.c b/drivers/thunderbolt/domain.c
> index b6f5079cdf6f..1564ce6fca37 100644
> --- a/drivers/thunderbolt/domain.c
> +++ b/drivers/thunderbolt/domain.c
> @@ -671,6 +671,32 @@ int tb_domain_runtime_resume(struct tb *tb)
> return 0;
> }
>
> +/**
> + * tb_domain_pause() - Pause the domain
> + * @tb: Domain to pause
> + *
> + * Blocks the connection manager and stops the control channel so that
> + * the caller can touch the host interface hardware behind its back.
> + * Takes @tb->lock.
> + *
> + * Once done whatever operations needed call tb_domain_unpause().
> + */
> +void tb_domain_pause(struct tb *tb)
> +{
> + mutex_lock(&tb->lock);
> + tb_ctl_stop(tb->ctl);
> +}
> +
> +/**
> + * tb_domain_unpause() - Resume paused domain
> + * @tb: Domain to unpause
> + */
> +void tb_domain_unpause(struct tb *tb)
> +{
> + tb_ctl_start(tb->ctl);
> + mutex_unlock(&tb->lock);
> +}
> +
> /**
> * tb_domain_disapprove_switch() - Disapprove switch
> * @tb: Domain the switch belongs to
> @@ -835,21 +861,6 @@ int tb_domain_approve_xdomain_paths(struct tb *tb, struct tb_xdomain *xd,
> transmit_ring, receive_path, receive_ring);
> }
>
> -static void tb_domain_reset_interface(struct tb *tb)
> -{
> - struct tb_nhi *nhi = tb->nhi;
> -
> - if (!nhi->ops->reset_interface)
> - return;
> -
> - guard(mutex)(&tb->lock);
> -
> - /* The reset clears the ring state so stop the control channel */
> - tb_ctl_stop(tb->ctl);
> - nhi->ops->reset_interface(nhi);
> - tb_ctl_start(tb->ctl);
> -}
> -
> /**
> * tb_domain_disconnect_xdomain_paths() - Disable DMA paths for XDomain
> * @tb: Domain disabling the DMA paths
> @@ -872,20 +883,11 @@ int tb_domain_disconnect_xdomain_paths(struct tb *tb, struct tb_xdomain *xd,
> int transmit_path, int transmit_ring,
> int receive_path, int receive_ring)
> {
> - int ret;
> -
> if (!tb->cm_ops->disconnect_xdomain_paths)
> return -ENOTSUPP;
>
> - ret = tb->cm_ops->disconnect_xdomain_paths(tb, xd, transmit_path,
> + return tb->cm_ops->disconnect_xdomain_paths(tb, xd, transmit_path,
> transmit_ring, receive_path, receive_ring);
> - if (ret)
> - return ret;
> -
> - if (tb->nhi->quirks & QUIRK_RESET_DMA_ON_TEARDOWN)
> - tb_domain_reset_interface(tb);
> -
> - return 0;
> }
>
> static int disconnect_xdomain(struct device *dev, void *data)
> diff --git a/drivers/thunderbolt/nhi.c b/drivers/thunderbolt/nhi.c
> index a7e6184cdfe1..423e7dba473c 100644
> --- a/drivers/thunderbolt/nhi.c
> +++ b/drivers/thunderbolt/nhi.c
> @@ -523,9 +523,45 @@ irqreturn_t ring_msix(int irq, void *data)
> return IRQ_HANDLED;
> }
>
> +static bool ring_is_dma(const struct tb_ring *ring)
> +{
> + return ring->hop >= RING_FIRST_USABLE_HOPID;
> +}
> +
> +static bool nhi_dma_rings_running(const struct tb_nhi *nhi)
> +{
> + int i;
> +
> + lockdep_assert_held(&nhi->lock);
> +
> + /*
> + * Holding nhi->lock is enough here because tb_ring_start() and
> + * tb_ring_stop() both hold it when they update ring->running.
> + */
> + for (i = RING_FIRST_USABLE_HOPID; i < nhi->hop_count; i++) {
> + if (nhi->tx_rings[i] && nhi->tx_rings[i]->running)
> + return true;
> + if (nhi->rx_rings[i] && nhi->rx_rings[i]->running)
> + return true;
> + }
> +
> + return false;
> +}
> +
> +static bool nhi_avoid_used_dma_rings(const struct tb_nhi *nhi)
> +{
> + lockdep_assert_held(&nhi->lock);
> +
> + if (!(nhi->quirks & QUIRK_RESET_DMA_ON_TEARDOWN))
> + return false;
> +
> + return nhi_dma_rings_running(nhi);
> +}
> +
> static int nhi_alloc_hop(struct tb_nhi *nhi, struct tb_ring *ring)
> {
> unsigned int start_hop = RING_FIRST_USABLE_HOPID;
> + bool avoid_used;
> int ret = 0;
>
> if (nhi->quirks & QUIRK_E2E) {
> @@ -539,6 +575,8 @@ static int nhi_alloc_hop(struct tb_nhi *nhi, struct tb_ring *ring)
>
> spin_lock_irq(&nhi->lock);
>
> + avoid_used = nhi_avoid_used_dma_rings(nhi);
> +
> if (ring->hop < 0) {
> unsigned int i;
>
> @@ -547,6 +585,8 @@ static int nhi_alloc_hop(struct tb_nhi *nhi, struct tb_ring *ring)
> * range 1 .. hop_count - 1.
> */
> for (i = start_hop; i < nhi->hop_count; i++) {
> + if (avoid_used && test_bit(i, nhi->dma_hops_used))
> + continue;
> if (ring->is_tx) {
> if (!nhi->tx_rings[i]) {
> ring->hop = i;
> @@ -559,6 +599,13 @@ static int nhi_alloc_hop(struct tb_nhi *nhi, struct tb_ring *ring)
> }
> }
> }
> +
> + if (ring->hop < 0 && avoid_used) {
> + dev_warn(nhi->dev,
> + "out of HopIDs that do not need a host interface reset\n");
> + ret = -EBUSY;
> + goto err_unlock;
> + }
> }
>
> if (ring->hop > 0 && ring->hop < start_hop) {
> @@ -583,6 +630,15 @@ static int nhi_alloc_hop(struct tb_nhi *nhi, struct tb_ring *ring)
> ret = -EBUSY;
> goto err_unlock;
> }
> + /* Automatic allocation above already skips the used HopIDs */
> + if (avoid_used && ring_is_dma(ring) &&
> + test_bit(ring->hop, nhi->dma_hops_used)) {
> + dev_warn(nhi->dev,
> + "hop %d needs a host interface reset before reuse\n",
> + ring->hop);
> + ret = -EBUSY;
> + goto err_unlock;
> + }
>
> if (ring->is_tx)
> nhi->tx_rings[ring->hop] = ring;
> @@ -710,6 +766,62 @@ struct tb_ring *tb_ring_alloc_rx(struct tb_nhi *nhi, int hop, int size,
> }
> EXPORT_SYMBOL_GPL(tb_ring_alloc_rx);
>
> +/**
> + * nhi_reset_interface() - Reset the host interface
> + * @nhi: Host interface to reset
> + *
> + * Brings the registers in the memory BAR back to their default state and
> + * clears the End-to-End Flow Control state. The caller is responsible for
> + * stopping the control channel over the reset because it clears the ring
> + * state as well.
> + */
> +static void nhi_reset_interface(struct tb_nhi *nhi)
> +{
> + u32 val;
> +
> + val = ioread32(nhi->iobase + REG_CAPS);
> + /* Only v1 host interfaces implement the reset */
> + if (FIELD_GET(REG_CAPS_VERSION_MASK, val) >= REG_CAPS_VERSION_2)
> + return;
> +
> + dev_dbg(nhi->dev, "issuing host interface reset\n");
> +
> + iowrite32(REG_HOST_INTERFACE_RESET_RST,
> + nhi->iobase + REG_HOST_INTERFACE_RESET);
> + /* Wait for tHIReset (10 ms) to complete */
> + usleep_range(10000, 20000);
> +}
> +
> +static void nhi_reset_quirk(struct tb_ring *ring)
> +{
> + struct tb_nhi *nhi = ring->nhi;
> + struct tb *tb = dev_get_drvdata(nhi->dev);
> +
> + if (!(nhi->quirks & QUIRK_RESET_DMA_ON_TEARDOWN))
> + return;
> + if (!ring_is_dma(ring))
> + return;
> +
> + scoped_guard(spinlock_irq, &nhi->lock) {
> + if (nhi->going_away)
> + return;
> + if (bitmap_empty(nhi->dma_hops_used, nhi->hop_count))
> + return;
> + /*
> + * If any of the DMA rings are still running we cannot
> + * do the reset.
> + */
> + if (nhi_dma_rings_running(nhi))
> + return;
> +
> + bitmap_zero(nhi->dma_hops_used, nhi->hop_count);
> + }
> +
> + /* CM must be blocked before host interface reset can be done */
> + scoped_guard(tb_domain_paused, tb)
> + nhi_reset_interface(nhi);
> +}
> +
> /**
> * tb_ring_start() - enable a ring
> * @ring: Ring to start
> @@ -721,6 +833,8 @@ void tb_ring_start(struct tb_ring *ring)
> u16 frame_size;
> u32 flags;
>
> + nhi_reset_quirk(ring);
> +
> spin_lock_irq(&ring->nhi->lock);
> spin_lock(&ring->lock);
> if (ring->nhi->going_away)
> @@ -781,6 +895,8 @@ void tb_ring_start(struct tb_ring *ring)
> if (!(ring->flags & RING_FLAG_NO_INTERRUPT))
> ring_interrupt_active(ring, true);
> ring->running = true;
> + if (ring->nhi->dma_hops_used && ring_is_dma(ring))
> + __set_bit(ring->hop, ring->nhi->dma_hops_used);
> err:
> spin_unlock(&ring->lock);
> spin_unlock_irq(&ring->nhi->lock);
> @@ -1241,32 +1357,6 @@ static void nhi_reset(struct tb_nhi *nhi)
> dev_warn(nhi->dev, "timeout resetting host router\n");
> }
>
> -/**
> - * nhi_reset_interface() - Reset the host interface
> - * @nhi: Host interface to reset
> - *
> - * Brings the registers in the memory BAR back to their default state and
> - * clears the End-to-End Flow Control state. The caller is responsible for
> - * stopping the control channel over the reset because it clears the ring
> - * state as well.
> - */
> -void nhi_reset_interface(struct tb_nhi *nhi)
> -{
> - u32 val;
> -
> - val = ioread32(nhi->iobase + REG_CAPS);
> - /* Only v1 host interfaces implement the reset */
> - if (FIELD_GET(REG_CAPS_VERSION_MASK, val) >= REG_CAPS_VERSION_2)
> - return;
> -
> - dev_dbg(nhi->dev, "issuing host interface reset\n");
> -
> - iowrite32(REG_HOST_INTERFACE_RESET_RST,
> - nhi->iobase + REG_HOST_INTERFACE_RESET);
> - /* Wait for tHIReset (10 ms) to complete */
> - usleep_range(10000, 20000);
> -}
> -
> static struct tb *nhi_select_cm(struct tb_nhi *nhi)
> {
> bool linked = false;
> @@ -1331,6 +1421,13 @@ int nhi_probe(struct tb_nhi *nhi)
> if (!nhi->tx_rings || !nhi->rx_rings || !nhi->interrupt_mask)
> return -ENOMEM;
>
> + if (nhi->quirks & QUIRK_RESET_DMA_ON_TEARDOWN) {
> + nhi->dma_hops_used = devm_bitmap_zalloc(dev, nhi->hop_count,
> + GFP_KERNEL);
> + if (!nhi->dma_hops_used)
> + return -ENOMEM;
> + }
> +
> nhi_reset(nhi);
>
> /* In case someone left them on. */
> diff --git a/drivers/thunderbolt/nhi.h b/drivers/thunderbolt/nhi.h
> index b2e2e2c413b2..53374c12b685 100644
> --- a/drivers/thunderbolt/nhi.h
> +++ b/drivers/thunderbolt/nhi.h
> @@ -36,7 +36,6 @@ irqreturn_t nhi_msi(int irq, void *data);
> irqreturn_t ring_msix(int irq, void *data);
> int nhi_probe(struct tb_nhi *nhi);
> void nhi_shutdown(struct tb_nhi *nhi);
> -void nhi_reset_interface(struct tb_nhi *nhi);
>
> extern const struct dev_pm_ops nhi_pm_ops;
>
> @@ -55,7 +54,6 @@ extern const struct dev_pm_ops nhi_pm_ops;
> * @release_ring_irq: NHI specific interrupt release hook
> * @is_present: Whether the device is currently present on the parent bus
> * @init_interrupts: NHI specific interrupt initialization hook
> - * @reset_interface: Resets the host interface
> */
> struct tb_nhi_ops {
> int (*init)(struct tb_nhi *nhi);
> @@ -71,7 +69,6 @@ struct tb_nhi_ops {
> void (*release_ring_irq)(struct tb_ring *ring);
> bool (*is_present)(struct tb_nhi *nhi);
> int (*init_interrupts)(struct tb_nhi *nhi);
> - void (*reset_interface)(struct tb_nhi *nhi);
> };
>
> /*
> diff --git a/drivers/thunderbolt/pci.c b/drivers/thunderbolt/pci.c
> index e40d4d6af071..0a586122db47 100644
> --- a/drivers/thunderbolt/pci.c
> +++ b/drivers/thunderbolt/pci.c
> @@ -357,7 +357,6 @@ static const struct tb_nhi_ops pci_nhi_default_ops = {
> .shutdown = nhi_pci_release_irq,
> .is_present = nhi_pci_is_present,
> .init_interrupts = nhi_pci_init_msi,
> - .reset_interface = nhi_reset_interface,
> };
>
> /* Ice Lake specific NHI operations */
> @@ -576,7 +575,6 @@ static const struct tb_nhi_ops icl_nhi_ops = {
> .release_ring_irq = nhi_pci_ring_release_msix,
> .is_present = nhi_pci_is_present,
> .init_interrupts = nhi_pci_init_msi,
> - .reset_interface = nhi_reset_interface,
> };
>
> static int nhi_pci_probe(struct pci_dev *pdev, const struct pci_device_id *id)
> diff --git a/drivers/thunderbolt/tb.h b/drivers/thunderbolt/tb.h
> index 1f78e2528c05..268bc7d90267 100644
> --- a/drivers/thunderbolt/tb.h
> +++ b/drivers/thunderbolt/tb.h
> @@ -826,6 +826,10 @@ int tb_domain_thaw_noirq(struct tb *tb);
> void tb_domain_complete(struct tb *tb);
> int tb_domain_runtime_suspend(struct tb *tb);
> int tb_domain_runtime_resume(struct tb *tb);
> +void tb_domain_pause(struct tb *tb);
> +void tb_domain_unpause(struct tb *tb);
> +DEFINE_GUARD(tb_domain_paused, struct tb *, tb_domain_pause(_T),
> + tb_domain_unpause(_T))
> int tb_domain_disapprove_switch(struct tb *tb, struct tb_switch *sw);
> int tb_domain_approve_switch(struct tb *tb, struct tb_switch *sw);
> int tb_domain_approve_switch_key(struct tb *tb, struct tb_switch *sw);
> diff --git a/include/linux/thunderbolt.h b/include/linux/thunderbolt.h
> index 69839a514433..e1c270496cf6 100644
> --- a/include/linux/thunderbolt.h
> +++ b/include/linux/thunderbolt.h
> @@ -537,6 +537,9 @@ void tb_service_properties_changed(struct tb_service *svc);
> * MSI-X is used.
> * @hop_count: Number of rings (end point hops) supported by NHI.
> * @quirks: NHI specific quirks if any
> + * @dma_hops_used: Bitmap of HopIDs that have been programmed after the
> + * last host interface reset. Used only with
> + * %QUIRK_RESET_DMA_ON_TEARDOWN.
> * @domain_released: Completed when domain has been fully released
> * @host_reset: Host router was reset on driver load, or forced on system
> * shutdown/reboot. When set, tb_stop() asserts DPR on connected
> @@ -557,6 +560,7 @@ struct tb_nhi {
> struct work_struct interrupt_work;
> u32 hop_count;
> unsigned long quirks;
> + unsigned long *dma_hops_used;
> struct completion domain_released;
> bool host_reset;
> };
next prev parent reply other threads:[~2026-09-09 19:06 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-25 21:42 [PATCH v2] " juan.martinez
2026-08-26 3:02 ` Mario Limonciello
2026-08-27 21:57 ` [PATCH v3] " Juan Martinez
2026-08-28 4:43 ` Mario Limonciello
2026-08-28 5:19 ` [PATCH v4] " Juan Martinez
2026-08-28 14:58 ` Mario Limonciello
2026-08-31 11:11 ` Mika Westerberg
2026-08-31 12:55 ` Mario Limonciello
2026-08-31 13:06 ` Mika Westerberg
2026-08-31 13:07 ` Mario Limonciello
2026-08-31 16:16 ` [PATCH v5] " juan.martinez
2026-09-01 22:16 ` Mario Limonciello
2026-09-02 5:48 ` Mika Westerberg
2026-09-09 19:06 ` Mario Limonciello [this message]
2026-09-10 14:19 ` S, Sanath
2026-09-10 17:24 ` Mario Limonciello
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=21cbfbaf-ef1f-469b-a33b-8d623dd7f9a3@kernel.org \
--to=superm1@kernel.org \
--cc=Juan.Martinez@amd.com \
--cc=Sanath.S@amd.com \
--cc=YehezkelShB@gmail.com \
--cc=andreas.noever@gmail.com \
--cc=basavaraj.natikar@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=westeri@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®