Linux PCI subsystem development
 help / color / mirror / Atom feed
From: Lukas Wunner <lukas@wunner.de>
To: fengnan chang <fengnanchang@gmail.com>
Cc: linux-pci@vger.kernel.org
Subject: Re: Deadlock during PCIe hot remove and SPDK exit
Date: Wed, 27 Nov 2024 08:10:43 +0100	[thread overview]
Message-ID: <Z0bF81fgwwc9wXJj@wunner.de> (raw)
In-Reply-To: <D0B37524-9444-423B-9E48-406CF9A29A6A@gmail.com>

On Wed, Nov 27, 2024 at 02:56:57PM +0800, fengnan chang wrote:
> Dear PCI maintainers:
>    I'm having a deadlock issue, somewhat similar to a previous one https://lore.kernel.org/linux-pci/CS1PR8401MB0728FC6FDAB8A35C22BD90EC95F10@CS1PR8401MB0728.NAMPRD84.PROD.OUTLOOK.COM/#t??? but my kernel (6.6.40) already included the fix f5eff55.

Could you try a contemporary kernel such as v6.12 and test if it
still exhibits the issue?


> irq/148-pciehp stack, cat /proc/513/stack
> [<0>] vfio_unregister_group_dev+0x97/0xe0 [vfio]     //wait for 
> [<0>] vfio_pci_core_unregister_device+0x19/0x80 [vfio_pci_core]
> [<0>] vfio_pci_remove+0x15/0x20 [vfio_pci]
> [<0>] pci_device_remove+0x39/0xb0
> [<0>] device_release_driver_internal+0xad/0x120
> [<0>] pci_stop_bus_device+0x5d/0x80
> [<0>] pci_stop_and_remove_bus_device+0xe/0x20
> [<0>] pciehp_unconfigure_device+0x91/0x160   //hold pci_rescan_remove_lock, release reset_lock of ctrl B 
> [<0>] pciehp_disable_slot+0x6b/0x130
> [<0>] pciehp_handle_presence_or_link_change+0x7d/0x4d0
> [<0>] pciehp_ist+0x236/0x260             //hold reset_lock of ctrl B

It says here "wait for".

Wait for what?  Why is vfio_unregister_group_dev() blocking?

Thanks,

Lukas

  reply	other threads:[~2024-11-27  7:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-27  6:56 Deadlock during PCIe hot remove and SPDK exit fengnan chang
2024-11-27  7:10 ` Lukas Wunner [this message]
2024-11-28  3:50 ` fengnan chang
2024-11-29  8:05   ` Yi Liu
2024-12-02  3:25     ` fengnan chang
2024-12-03  5:36       ` Yi Liu
2024-12-03  9:31         ` fengnan chang

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=Z0bF81fgwwc9wXJj@wunner.de \
    --to=lukas@wunner.de \
    --cc=fengnanchang@gmail.com \
    --cc=linux-pci@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