summaryrefslogtreecommitdiff
path: root/kernel
diff options
context:
space:
mode:
authorNiklas Schnelle <schnelle@linux.ibm.com>2020-09-03 13:42:57 +0200
committerVasily Gorbik <gor@linux.ibm.com>2020-09-14 10:08:07 +0200
commitafdf9550e54627fcf4dd609bdc1153059378cdf5 (patch)
treeb958e58ec35514562fbc6b78977a54c7075ef85a /kernel
parentfcb2b70cdb194157678fb1a75f9ff499aeba3d2a (diff)
s390/pci: fix leak of DMA tables on hard unplug
commit f606b3ef47c9 ("s390/pci: adapt events for zbus") removed the zpci_disable_device() call for a zPCI event with PEC 0x0304 because the device is already deconfigured by the platform. This however skips the Linux side of the disable in particular it leads to leaking the DMA tables and bitmaps because zpci_dma_exit_device() is never called on the device. If the device transitions to the Reserved state we call zpci_zdev_put() but zpci_release_device() will not call zpci_disable_device() because the state of the zPCI function is already ZPCI_FN_STATE_STANDBY. If the device is put into the Standby state, zpci_disable_device() is not called and the device is assumed to have been put in Standby through platform action. At this point the device may be removed by a subsequent event with PEC 0x0308 or 0x0306 which calls zpci_zdev_put() with the same problem as above or the device may be configured again in which case zpci_disable_device() is also not called. Fix this by calling zpci_disable_device() explicitly for PEC 0x0304 as before. To make it more clear that zpci_disable_device() may be called, even if the lower level device has already been disabled by the platform, add a comment to zpci_disable_device(). Cc: <stable@vger.kernel.org> # 5.8 Fixes: f606b3ef47c9 ("s390/pci: adapt events for zbus") Signed-off-by: Niklas Schnelle <schnelle@linux.ibm.com> Signed-off-by: Vasily Gorbik <gor@linux.ibm.com>
Diffstat (limited to 'kernel')
0 files changed, 0 insertions, 0 deletions