From: Bjorn Helgaas <helgaas@kernel.org>
To: Hans de Goede <hdegoede@redhat.com>
Cc: Dan Williams <dan.j.williams@intel.com>,
bhelgaas@google.com, Dave Jiang <dave.jiang@intel.com>,
Imre Deak <imre.deak@intel.com>,
Jani Saarinen <jani.saarinen@intel.com>,
linux-pci@vger.kernel.org, linux-cxl@vger.kernel.org
Subject: Re: [PATCH v2 0/3] PCI: Revert / replace the cfg_access_lock lockdep mechanism
Date: Mon, 3 Jun 2024 15:37:12 -0500 [thread overview]
Message-ID: <20240603203712.GA692178@bhelgaas> (raw)
In-Reply-To: <6daf3a21-6e78-4a82-b03f-af9462fad012@redhat.com>
On Mon, Jun 03, 2024 at 09:49:39PM +0200, Hans de Goede wrote:
> Hi,
>
> On 5/31/24 3:04 AM, Dan Williams wrote:
> > Changes since v1 [1]:
> > - split out the new warning into its own patch (Bjorn)
> > - include the provisional fix to the pci_reset_bus() path
> >
> > [1]: http://lore.kernel.org/r/171709637423.1568751.11773767969980847536.stgit@dwillia2-xfh.jf.intel.com
> >
> > Hi Bjorn,
> >
> > Here is the targeted revert of the cfg_access_lock lockdep
> > infrastructure, but with the new proposed warning for catching "unlocked
> > pci_bridge_secondary_bus_reset()" events broken out into its own change.
> > I also included the proposed fix for at least one known case where
> > pci_bridge_secondary_bus_reset() is being called without
> > cfg_access_lock.
> >
> > Given there may be more cases to unwind, and the fact that I am not
> > convinced patch3 will be problem free I would, as you suggested,
> > consider patch2 and patch3 v6.11 material. Patch1 is urgent for v6.10-rc
> > to put out these lockdep false positive reports.
>
> I can confirm that this series fixes the lockdep errors which
> I was seeing:
>
> Tested-by: Hans de Goede <hdegoede@redhat.com>
Added to the three patches in this series, thanks, Hans!
> > ---
> >
> > Dan Williams (3):
> > PCI: Revert the cfg_access_lock lockdep mechanism
> > PCI: Warn on missing cfg_access_lock during secondary bus reset
> > PCI: Add missing bridge lock to pci_bus_lock()
> >
> >
> > drivers/pci/access.c | 4 ----
> > drivers/pci/pci.c | 8 +++++++-
> > drivers/pci/probe.c | 3 ---
> > include/linux/lockdep.h | 5 -----
> > include/linux/pci.h | 2 --
> > 5 files changed, 7 insertions(+), 15 deletions(-)
> >
> > base-commit: 56fb6f92854f29dcb6c3dc3ba92eeda1b615e88c
> >
>
prev parent reply other threads:[~2024-06-03 20:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-31 1:04 [PATCH v2 0/3] PCI: Revert / replace the cfg_access_lock lockdep mechanism Dan Williams
2024-05-31 1:04 ` [PATCH v2 1/3] PCI: Revert " Dan Williams
2024-05-31 18:05 ` Dave Jiang
2024-06-04 8:03 ` Kalle Valo
2024-06-04 17:11 ` Bjorn Helgaas
2024-06-06 10:04 ` Leon Romanovsky
2024-05-31 1:04 ` [PATCH v2 2/3] PCI: Warn on missing cfg_access_lock during secondary bus reset Dan Williams
2024-05-31 18:06 ` Dave Jiang
2024-05-31 1:04 ` [PATCH v2 3/3] PCI: Add missing bridge lock to pci_bus_lock() Dan Williams
2024-05-31 18:07 ` Dave Jiang
2024-06-28 19:25 ` Keith Busch
2024-05-31 21:31 ` [PATCH v2 0/3] PCI: Revert / replace the cfg_access_lock lockdep mechanism Bjorn Helgaas
2024-06-03 19:49 ` Hans de Goede
2024-06-03 20:37 ` Bjorn Helgaas [this message]
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=20240603203712.GA692178@bhelgaas \
--to=helgaas@kernel.org \
--cc=bhelgaas@google.com \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=hdegoede@redhat.com \
--cc=imre.deak@intel.com \
--cc=jani.saarinen@intel.com \
--cc=linux-cxl@vger.kernel.org \
--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