Hi Matthew,
I'm updating the hirsute entry to Fix Committed, since the 5.10 kernel is in
hirsute-proposed
and the requested patch is included:
Ubuntu-5.10.0-12.13
v5.10
So we are good with 21.04/hirsute.
And it's great that see that you've managed to get it accepted via upstream
stable, since this provides a lot of confidence about the fix that we need for
an LTS SRU - and since we have a process in place to pick up stable (upstream)
updates, that will find (semi-automatically) it's way into 20.04/focal's Ubuntu
kernel 5.4 soon.
So this is highly appreciated.
However, to avoid any regression for people who upgrade from an Ubuntu release
n to n+1 (in this case 20.04/focal to 20.10/groovy) one requirement of our SRU
process is to get the patches in to the Ubuntu releases/kernels starting from
newest to the oldest Ubuntu release the patch needs to be applied to.
Hence me trying to get the patch applied to the groovy master-next tree, based
on kernel 5.8, which failed (LP comment #2) (since we knew it's already in 5.10
which is the target for 21.04).
Well, I can retry to apply the patch to groovy master-next, since the groovy
master-next tree evolved over time, but I guess it still does not apply - hence
me asking for a backport (#2)
Btw. even if 5.8.y ran out of upstream stable support, we still look at the
5.9.y stable updates for inclusion into 5.8. So tagging the fix for stable
5.9.y would be an option, too.
** Changed in: linux (Ubuntu Hirsute)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Focal)
Status: Incomplete => Confirmed
** Changed in: ubuntu-z-systems
Status: Incomplete => Confirmed
--
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/1907421
Title:
[UBUNTU 21.04] vfio: pass DMA availability information to userspace
Status in Ubuntu on IBM z Systems:
Confirmed
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Focal:
Confirmed
Status in linux source package in Groovy:
Incomplete
Status in linux source package in Hirsute:
Fix Committed
Bug description:
Description: vfio: pass DMA availability information to userspace
Symptom: vfio-pci device on s390 enters error state
Problem: Commit 492855939bdb added a limit to the number of concurrent
DMA requests for a vfio container. However, lazy unmapping in
s390 can in fact cause quite a large number of outstanding DMA
requests to build up prior to being purged, potentially the
entire guest DMA space. This results in unexpected errors seen
in qemu such as 'VFIO_MAP_DMA failed: No space left on device'
Solution: The solution requires a change to both kernel and qemu - For
the kernel, add the ability to provide the number of allowable
DMA requests via the VFIO_IOMMU_GET_INFO ioctl.
Reproduction: Put a vfio-pci device on s390 under I/O load
Upstream-ID: a717072007e8aedd3f951726d8cf55454860b30d
7d6e1329652ed971d1b6e0e7bea66fba5044e271
Need also to be integrated into 20.10 and 20.04.
OK, just to clarify we don't need to fix bionic for this one, but
rather focal (20.04) and groovy (20.10). Furthermore, for 20.04,
20.10 and 21.04 ONLY commit 7d6e1329652ed971d1b6e0e7bea66fba5044e271
is needed, the other was a pre-req that is already present.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1907421/+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
