diff options
author | Christoph Hellwig <hch@lst.de> | 2017-06-01 14:10:37 +0300 |
---|---|---|
committer | Bjorn Helgaas <bhelgaas@google.com> | 2017-06-15 05:49:13 +0300 |
commit | b014e96d1abbd67404bbe2018937b46466299e9e (patch) | |
tree | 38b5d4431d8a8305423cc010443ceecb8ad8bde4 /drivers/nvme/host/pci.c | |
parent | 17530e71e0166a37f8e20a9b7bcf1d50ae3cff8e (diff) | |
download | linux-b014e96d1abbd67404bbe2018937b46466299e9e.tar.xz |
PCI: Protect pci_error_handlers->reset_notify() usage with device_lock()
Every method in struct device_driver or structures derived from it like
struct pci_driver MUST provide exclusion vs the driver's ->remove() method,
usually by using device_lock().
Protect use of pci_error_handlers->reset_notify() by holding the device
lock while calling it.
Note:
- pci_dev_lock() calls device_lock() in addition to blocking user-space
config accesses.
- pci_err_handlers->reset_notify() is used inside
pci_dev_save_and_disable() and pci_dev_restore(). We could hold the
device lock directly in pci_reset_notify(), but we expand the region
since we have several calls following each other.
Without this, ->reset_notify() may race with ->remove() calls, which can be
easily triggered in NVMe.
[bhelgaas: changelog, add pci_reset_notify() comment]
[bhelgaas: fold in fix from Dan Carpenter <dan.carpenter@oracle.com>:
http://lkml.kernel.org/r/20170701135323.x5vaj4e2wcs2mcro@mwanda]
Link: http://lkml.kernel.org/r/20170601111039.8913-2-hch@lst.de
Reported-by: Rakesh Pandit <rakesh@tuxera.com>
Tested-by: Rakesh Pandit <rakesh@tuxera.com>
Signed-off-by: Christoph Hellwig <hch@lst.de>
Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>
Diffstat (limited to 'drivers/nvme/host/pci.c')
0 files changed, 0 insertions, 0 deletions