[UBUNTU 20.04] virtio-blk disks can go dissfunctional when swiotlb fills up
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
The Ubuntu-power-systems project |
Fix Released
|
Critical
|
Frank Heimes | ||
linux (Ubuntu) |
Fix Released
|
Undecided
|
Frank Heimes |
Bug Description
virtio-blk disks can go dissfunctional when swiotlb fills up
virtio-blk hw queue gets possibly permanently stopped when swiotlb full
For example, with a PV guest choose a small swiotlb (30MB) and create IO load on several virtio-blk disks simultaneously. It actually should not matter what causes the swiotlb pressure (can be virtio-net as well).
Fixes posted upstream:
https:/
We will need backports to support Protected Virtualization.
IBM verified that the patches apply cleanly on focal/master-next, upstream commit ids for reference:
commit bab7e6f05699a48
Author: Halil Pasic <email address hidden>
Date: Thu Feb 13 13:37:27 2020 +0100
virtio-blk: fix hw_queue stopped on arbitrary error
commit 24506976aec9205
Author: Halil Pasic <email address hidden>
Date: Thu Feb 13 13:37:28 2020 +0100
virtio-blk: improve virtqueue error to BLK_STS
Also applies cleanly on 19.10.....
CVE References
tags: | added: architecture-all bugnameltc-184224 severity-critical targetmilestone-inin2004 |
Changed in ubuntu: | |
assignee: | nobody → Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) |
affects: | ubuntu → linux (Ubuntu) |
Changed in ubuntu-power-systems: | |
assignee: | nobody → Canonical Kernel Team (canonical-kernel-team) |
importance: | Undecided → Critical |
Changed in ubuntu-power-systems: | |
status: | New → Triaged |
description: | updated |
summary: |
- [UBUNTU 20.04] virtio-blk hw queue gets possibly permanently stopped - when swiotlb full + [UBUNTU 20.04] virtio-blk disks can go dissfunctional when swiotlb fills + up |
Changed in linux (Ubuntu): | |
status: | In Progress → Fix Committed |
Changed in ubuntu-power-systems: | |
status: | In Progress → Fix Committed |
Changed in ubuntu-power-systems: | |
status: | Fix Committed → Fix Released |
Found the two commits in 'linux-next' ...