summaryrefslogtreecommitdiffstats
path: root/lib/Kconfig.kasan
diff options
context:
space:
mode:
authorJakub Kicinski <jakub.kicinski@netronome.com>2017-05-22 15:50:23 -0700
committerBjorn Helgaas <bhelgaas@google.com>2017-06-14 17:41:19 -0500
commit17530e71e0166a37f8e20a9b7bcf1d50ae3cff8e (patch)
tree985e0214ae3fae454db01acfdc1566d3c9d89798 /lib/Kconfig.kasan
parentd40b7fd2cbcbeeff36e52aef2aa44e03a2ab7345 (diff)
downloadlinux-17530e71e0166a37f8e20a9b7bcf1d50ae3cff8e.tar.bz2
PCI: Protect pci_driver->sriov_configure() 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_driver->sriov_configure() by holding the device lock while calling it. The PCI core sets the pci_dev->driver pointer in local_pci_probe() before calling ->probe() and only clears it after ->remove(). This means driver's ->sriov_configure() callback will happily race with probe() and remove(), most likely leading to BUGs, since drivers don't expect this. Remove the iov lock completely, since we remove the last user. [bhelgaas: changelog, thanks to Christoph for locking rule] Link: http://lkml.kernel.org/r/20170522225023.14010-1-jakub.kicinski@netronome.com Signed-off-by: Jakub Kicinski <jakub.kicinski@netronome.com> Signed-off-by: Bjorn Helgaas <bhelgaas@google.com> Reviewed-by: Christoph Hellwig <hch@lst.de>
Diffstat (limited to 'lib/Kconfig.kasan')
0 files changed, 0 insertions, 0 deletions