From: Anatoli Antonovitch <anatoli.antonovitch@amd.com>
To: Lukas Wunner <lukas@wunner.de>
Cc: Anatoli Antonovitch <a.antonovitch@gmail.com>,
linux-pci@vger.kernel.org, bhelgaas@google.com,
Alexander.Deucher@amd.com, christian.koenig@amd.com
Subject: Re: [PATCH] PCI/hotplug: Replaced down_write_nested with hotplug_slot_rwsem if ctrl->depth > 0 when taking the ctrl->reset_lock.
Date: Mon, 23 Jan 2023 14:30:03 -0500 [thread overview]
Message-ID: <22a64441-5eed-8d56-5c5e-80c425cf6967@amd.com> (raw)
In-Reply-To: <20230121072148.GA13969@wunner.de>
I do not see a deadlock, when applying the following old patch:
https://lore.kernel.org/linux-pci/908047f7699d9de9ec2efd6b79aa752d73dab4b6.1595329748.git.lukas@wunner.de/
after merge for the kernel 6.2.0-rc5, and applied the alternative patch:
https://patchwork.kernel.org/project/linux-pci/patch/3dc88ea82bdc0e37d9000e413d5ebce481cbd629.1674205689.git.lukas@wunner.de/
I have uploaded the merged patch and the system log for the upstream kernel.
Anatoli
On 2023-01-21 02:21, Lukas Wunner wrote:
> You're now getting a different deadlock. That one is addressed by this
> old patch (it's already linked from the bugzilla):
>
> https://lore.kernel.org/linux-pci/908047f7699d9de9ec2efd6b79aa752d73dab4b6.1595329748.git.lukas@wunner.de/
>
> If you apply that patch plus the new one, do you still see a deadlock?
next prev parent reply other threads:[~2023-01-23 19:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-13 17:01 [PATCH] PCI/hotplug: Replaced down_write_nested with hotplug_slot_rwsem if ctrl->depth > 0 when taking the ctrl->reset_lock Anatoli Antonovitch
2023-01-20 9:28 ` Lukas Wunner
2023-01-20 21:35 ` Anatoli Antonovitch
2023-01-21 7:21 ` Lukas Wunner
2023-01-23 19:30 ` Anatoli Antonovitch [this message]
2023-02-13 14:59 ` Anatoli Antonovitch
2023-02-17 16:03 ` Bjorn Helgaas
2023-02-17 18:37 ` Deucher, Alexander
2023-02-19 20:21 ` Lukas Wunner
2023-04-10 20:36 ` Anatoli Antonovitch
-- strict thread matches above, loose matches on Subject: below --
2023-01-05 18:43 Anatoli Antonovitch
2023-01-05 19:18 ` Bjorn Helgaas
[not found] ` <5b9a2dc7-54ab-82c5-81e7-1770a4ec891c@amd.com>
2023-01-16 18:37 ` Bjorn Helgaas
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=22a64441-5eed-8d56-5c5e-80c425cf6967@amd.com \
--to=anatoli.antonovitch@amd.com \
--cc=Alexander.Deucher@amd.com \
--cc=a.antonovitch@gmail.com \
--cc=bhelgaas@google.com \
--cc=christian.koenig@amd.com \
--cc=linux-pci@vger.kernel.org \
--cc=lukas@wunner.de \
/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;
as well as URLs for NNTP newsgroup(s).