Patch request submitted for groovy:
https://lists.ubuntu.com/archives/kernel-team/2020-September/thread.html#113599
changing status to 'In Progress' for groovy.
** Changed in: linux (Ubuntu Groovy)
Status: New => In Progress
** Changed in: ubuntu-z-systems
Status: New => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1896216
Title:
[Ubuntu 20.10] zPCI DMA tables and bitmap leak on hard unplug (PCI
Event 0x0304)
Status in Ubuntu on IBM z Systems:
In Progress
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Focal:
New
Status in linux source package in Groovy:
In Progress
Bug description:
Commit "s390/pci: adapt events for zbus" removed the
zpci_disable_device() call for a zPCI event with PEC 0x0304 (hot
unplug) becausethe 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.
This has been fixed in the following commit (currently in linux-next)
afdf9550e54627fcf4dd609bdc1153059378cdf5 s390/pci: fix leak of DMA
tables on hard unplug
The commit re-introduces the zpci_disable_device() call as it was before the
zbus introduction, for good measure I also added a comment to
zpci_disable_device()
to call out the fact that it may be called with the device disabled
already.
As the commit was introduced with the multi-function support
this of course should go into both 20.10 and 20.04.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1896216/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
