Linux PCI subsystem development
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: Lukas Wunner <lukas@wunner.de>
Cc: Michael Haeuptle <michael.haeuptle@hpe.com>,
	Ian May <ian.may@canonical.com>,
	Andrey Grodzovsky <andrey2805@gmail.com>,
	Rahul Kumar <rahul.kumar1@amd.com>,
	Jialin Zhang <zhangjialin11@huawei.com>,
	Anatoli Antonovitch <Anatoli.Antonovitch@amd.com>,
	linux-pci@vger.kernel.org, Dan Stein <dstein@hpe.com>,
	Ashok Raj <ashok.raj@intel.com>,
	Alex Michon <amichon@kalrayinc.com>,
	Xiongfeng Wang <wangxiongfeng2@huawei.com>,
	Alex Williamson <alex.williamson@redhat.com>,
	Mika Westerberg <mika.westerberg@linux.intel.com>,
	Sathyanarayanan Kuppuswamy 
	<sathyanarayanan.kuppuswamy@linux.intel.com>
Subject: Re: [PATCH v2] PCI: pciehp: Fix AB-BA deadlock between reset_lock and device_lock
Date: Tue, 11 Apr 2023 13:24:12 -0500	[thread overview]
Message-ID: <20230411182412.GA4165673@bhelgaas> (raw)
In-Reply-To: <fef2b2e9edf245c049a8c5b94743c0f74ff5008a.1681191902.git.lukas@wunner.de>

On Tue, Apr 11, 2023 at 08:21:02AM +0200, Lukas Wunner wrote:
> In 2013, commits
> 
>   2e35afaefe64 ("PCI: pciehp: Add reset_slot() method")
>   608c388122c7 ("PCI: Add slot reset option to pci_dev_reset()")
> 
> amended PCIe hotplug to mask Presence Detect Changed events during a
> Secondary Bus Reset.  The reset thus no longer causes gratuitous slot
> bringdown and bringup.
> 
> However the commits neglected to serialize reset with code paths reading
> slot registers.  For instance, a slot bringup due to an earlier hotplug
> event may see the Presence Detect State bit cleared during a concurrent
> Secondary Bus Reset.
> ...

> Signed-off-by: Lukas Wunner <lukas@wunner.de>

Applied to pci/hotplug for v6.4, thanks!

> Cc: stable@vger.kernel.org # v4.19+
> Cc: Dan Stein <dstein@hpe.com>
> Cc: Ashok Raj <ashok.raj@intel.com>
> Cc: Alex Michon <amichon@kalrayinc.com>
> Cc: Xiongfeng Wang <wangxiongfeng2@huawei.com>
> Cc: Alex Williamson <alex.williamson@redhat.com>
> Cc: Mika Westerberg <mika.westerberg@linux.intel.com>
> Cc: Sathyanarayanan Kuppuswamy <sathyanarayanan.kuppuswamy@linux.intel.com>
> ---
> Link to v1:
> https://lore.kernel.org/linux-pci/908047f7699d9de9ec2efd6b79aa752d73dab4b6.1595329748.git.lukas@wunner.de/
> 
> In v1 I tried to solve the problem by changing the locking order for
> Secondary Bus Resets.  That didn't really work out.  I've experimented
> with various other approaches and finally came up with this simple one
> which lends itself well for backporting to stable.  I apologize for the
> long time this has taken.
> 
>  drivers/pci/hotplug/pciehp_pci.c | 15 +++++++++++++++
>  1 file changed, 15 insertions(+)
> 
> diff --git a/drivers/pci/hotplug/pciehp_pci.c b/drivers/pci/hotplug/pciehp_pci.c
> index d17f3bf..ad12515 100644
> --- a/drivers/pci/hotplug/pciehp_pci.c
> +++ b/drivers/pci/hotplug/pciehp_pci.c
> @@ -63,7 +63,14 @@ int pciehp_configure_device(struct controller *ctrl)
>  
>  	pci_assign_unassigned_bridge_resources(bridge);
>  	pcie_bus_configure_settings(parent);
> +
> +	/*
> +	 * Release reset_lock during driver binding
> +	 * to avoid AB-BA deadlock with device_lock.
> +	 */
> +	up_read(&ctrl->reset_lock);
>  	pci_bus_add_devices(parent);
> +	down_read_nested(&ctrl->reset_lock, ctrl->depth);
>  
>   out:
>  	pci_unlock_rescan_remove();
> @@ -104,7 +111,15 @@ void pciehp_unconfigure_device(struct controller *ctrl, bool presence)
>  	list_for_each_entry_safe_reverse(dev, temp, &parent->devices,
>  					 bus_list) {
>  		pci_dev_get(dev);
> +
> +		/*
> +		 * Release reset_lock during driver unbinding
> +		 * to avoid AB-BA deadlock with device_lock.
> +		 */
> +		up_read(&ctrl->reset_lock);
>  		pci_stop_and_remove_bus_device(dev);
> +		down_read_nested(&ctrl->reset_lock, ctrl->depth);
> +
>  		/*
>  		 * Ensure that no new Requests will be generated from
>  		 * the device.
> -- 
> 2.39.1
> 

      reply	other threads:[~2023-04-11 18:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-11  6:21 [PATCH v2] PCI: pciehp: Fix AB-BA deadlock between reset_lock and device_lock Lukas Wunner
2023-04-11 18:24 ` 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=20230411182412.GA4165673@bhelgaas \
    --to=helgaas@kernel.org \
    --cc=Anatoli.Antonovitch@amd.com \
    --cc=alex.williamson@redhat.com \
    --cc=amichon@kalrayinc.com \
    --cc=andrey2805@gmail.com \
    --cc=ashok.raj@intel.com \
    --cc=dstein@hpe.com \
    --cc=ian.may@canonical.com \
    --cc=linux-pci@vger.kernel.org \
    --cc=lukas@wunner.de \
    --cc=michael.haeuptle@hpe.com \
    --cc=mika.westerberg@linux.intel.com \
    --cc=rahul.kumar1@amd.com \
    --cc=sathyanarayanan.kuppuswamy@linux.intel.com \
    --cc=wangxiongfeng2@huawei.com \
    --cc=zhangjialin11@huawei.com \
    /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