Re: [PATCH] PCI: ensure the PCI device is locked over ->reset_notify calls

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: Re: [PATCH] PCI: ensure the PCI device is locked over ->reset_notify calls
From: Christoph Hellwig <hch@xxxxxx>
Date: Thu, 1 Jun 2017 12:46:01 +0200
Cc: Christoph Hellwig <hch@xxxxxx>, rakesh@xxxxxxxxxx, linux-pci@xxxxxxxxxxxxxxx, linux-nvme@xxxxxxxxxxxxxxxxxxx, Alex Williamson <alex.williamson@xxxxxxxxxx>
In-reply-to: <20170531165131.GA4496@bhelgaas-glaptop.roam.corp.google.com>
User-agent: Mutt/1.5.17 (2007-11-01)

On Wed, May 31, 2017 at 11:51:31AM -0500, Bjorn Helgaas wrote:
> Do you have any thoughts on whether the paths I mentioned above are
> also susceptible?

At least in theory ever method call that doesn't have the device
locked is susceptible, so yes.

References:
- avoid null pointer rereference during FLR
  - From: Christoph Hellwig
- [PATCH] PCI: ensure the PCI device is locked over ->reset_notify calls
  - From: Christoph Hellwig
- Re: [PATCH] PCI: ensure the PCI device is locked over ->reset_notify calls
  - From: Bjorn Helgaas
- Re: [PATCH] PCI: ensure the PCI device is locked over ->reset_notify calls
  - From: Christoph Hellwig
- Re: [PATCH] PCI: ensure the PCI device is locked over ->reset_notify calls
  - From: Bjorn Helgaas

Prev by Date: [PATCH] PCI: rockchip: Handle return value of clk_prepare_enable
Next by Date: avoid null pointer rereference during FLR V2
Previous by thread: Re: [PATCH] PCI: ensure the PCI device is locked over ->reset_notify calls
Next by thread: [PATCH v3] PCI: use IDA to manage domain number if not getting it from DT
Index(es):
- Date
- Thread

[Index of Archives] [DMA Engine] [Linux Coverity] [Linux USB] [Video for Linux] [Linux Audio Users] [Yosemite News] [Linux Kernel] [Linux SCSI] [Greybus]

Powered by Linux