Linux PCI subsystem development
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: Keith Busch <kbusch@meta.com>
Cc: linux-pci@vger.kernel.org, bhelgaas@google.com,
	kwilczynski@kernel.org, Keith Busch <kbusch@kernel.org>,
	Dan Williams <dan.j.williams@intel.com>,
	Hans de Goede <hdegoede@redhat.com>,
	Kalle Valo <kvalo@kernel.org>, Dave Jiang <dave.jiang@intel.com>
Subject: Re: [PATCHv2] PCI: fix recursive device locking
Date: Thu, 11 Jul 2024 15:50:44 -0500	[thread overview]
Message-ID: <20240711205044.GA296163@bhelgaas> (raw)
In-Reply-To: <20240711193650.701834-1-kbusch@meta.com>

[+cc Hans, Kalle, Dave]

On Thu, Jul 11, 2024 at 12:36:50PM -0700, Keith Busch wrote:
> From: Keith Busch <kbusch@kernel.org>
> 
> If one of the bus' devices has subordinates, the recursive call locks
> itself, so no need to lock the device before the recursion or it will
> surely deadlock.
> 
> Fixes: dbc5b5c0d268f87 ("PCI: Add missing bridge lock to pci_bus_lock()"
> Cc: Dan Williams <dan.j.williams@intel.com>
> Signed-off-by: Keith Busch <kbusch@kernel.org>

dbc5b5c0d268f87 was queued for the v6.11 merge window on pci/reset, so
I squashed this fix into that commit.  Thanks for the fix!

Hans, Kalle, Dave, I retained your Tested-by and Reviewed-by from
dbc5b5c0d268f87.  Please let me know if you want to update or remove
those.

> ---
> Changes from v1:
> 
>  Fixed the same recursive locking for pci_bus_trylock(),
>  pci_slot_lock(), and pci_slot_trylock()
> 
>  drivers/pci/pci.c | 33 ++++++++++++++++++---------------
>  1 file changed, 18 insertions(+), 15 deletions(-)
> 
> diff --git a/drivers/pci/pci.c b/drivers/pci/pci.c
> index df550953fa260..82b74d3f6bb1e 100644
> --- a/drivers/pci/pci.c
> +++ b/drivers/pci/pci.c
> @@ -5488,9 +5488,10 @@ static void pci_bus_lock(struct pci_bus *bus)
>  
>  	pci_dev_lock(bus->self);
>  	list_for_each_entry(dev, &bus->devices, bus_list) {
> -		pci_dev_lock(dev);
>  		if (dev->subordinate)
>  			pci_bus_lock(dev->subordinate);
> +		else
> +			pci_dev_lock(dev);
>  	}
>  }
>  
> @@ -5502,7 +5503,8 @@ static void pci_bus_unlock(struct pci_bus *bus)
>  	list_for_each_entry(dev, &bus->devices, bus_list) {
>  		if (dev->subordinate)
>  			pci_bus_unlock(dev->subordinate);
> -		pci_dev_unlock(dev);
> +		else
> +			pci_dev_unlock(dev);
>  	}
>  	pci_dev_unlock(bus->self);
>  }
> @@ -5512,16 +5514,15 @@ static int pci_bus_trylock(struct pci_bus *bus)
>  {
>  	struct pci_dev *dev;
>  
> -	pci_dev_lock(bus->self);
> +	if (!pci_dev_trylock(bus->self))
> +		return 0;
> +
>  	list_for_each_entry(dev, &bus->devices, bus_list) {
> -		if (!pci_dev_trylock(dev))
> -			goto unlock;
>  		if (dev->subordinate) {
> -			if (!pci_bus_trylock(dev->subordinate)) {
> -				pci_dev_unlock(dev);
> +			if (!pci_bus_trylock(dev->subordinate))
>  				goto unlock;
> -			}
> -		}
> +		} else if (!pci_dev_trylock(dev))
> +			goto unlock;
>  	}
>  	return 1;
>  
> @@ -5529,7 +5530,8 @@ static int pci_bus_trylock(struct pci_bus *bus)
>  	list_for_each_entry_continue_reverse(dev, &bus->devices, bus_list) {
>  		if (dev->subordinate)
>  			pci_bus_unlock(dev->subordinate);
> -		pci_dev_unlock(dev);
> +		else
> +			pci_dev_unlock(dev);
>  	}
>  	pci_dev_unlock(bus->self);
>  	return 0;
> @@ -5563,9 +5565,10 @@ static void pci_slot_lock(struct pci_slot *slot)
>  	list_for_each_entry(dev, &slot->bus->devices, bus_list) {
>  		if (!dev->slot || dev->slot != slot)
>  			continue;
> -		pci_dev_lock(dev);
>  		if (dev->subordinate)
>  			pci_bus_lock(dev->subordinate);
> +		else
> +			pci_dev_lock(dev);
>  	}
>  }
>  
> @@ -5591,14 +5594,13 @@ static int pci_slot_trylock(struct pci_slot *slot)
>  	list_for_each_entry(dev, &slot->bus->devices, bus_list) {
>  		if (!dev->slot || dev->slot != slot)
>  			continue;
> -		if (!pci_dev_trylock(dev))
> -			goto unlock;
>  		if (dev->subordinate) {
>  			if (!pci_bus_trylock(dev->subordinate)) {
>  				pci_dev_unlock(dev);
>  				goto unlock;
>  			}
> -		}
> +		} else if (!pci_dev_trylock(dev))
> +			goto unlock;
>  	}
>  	return 1;
>  
> @@ -5609,7 +5611,8 @@ static int pci_slot_trylock(struct pci_slot *slot)
>  			continue;
>  		if (dev->subordinate)
>  			pci_bus_unlock(dev->subordinate);
> -		pci_dev_unlock(dev);
> +		else
> +			pci_dev_unlock(dev);
>  	}
>  	return 0;
>  }
> -- 
> 2.43.0
> 

      parent reply	other threads:[~2024-07-11 20:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-11 19:36 [PATCHv2] PCI: fix recursive device locking Keith Busch
2024-07-11 20:05 ` Dan Williams
2024-07-11 20:50 ` 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=20240711205044.GA296163@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=kbusch@kernel.org \
    --cc=kbusch@meta.com \
    --cc=kvalo@kernel.org \
    --cc=kwilczynski@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