I check the situation in the different git trees (upstream and the ones
for the relevant Ubuntu releases) and the outcome is:
The commit a3e03bc1368c ("KVM: s390: index kvm->arch.idle_mask by
vcpu_idx") is upstream since v5.15-rc1, hence jammy does not need to be
patched, since it's target kernel version is 5.15, hence setting the
'affects jammy' entry to Fix Released.
I found the commit (here with hash 3cde6b00247a) in impish master.
It landed there based on https://bugs.launchpad.net/bugs/1946247 "Impish
update: v5.13.17 upstream stable release" and is tagged with
Ubuntu-5.13.0-21.21 and since there is 5.13.0.21.32 in impish-updates, the
patch is already rolled out for impish, hence marking the 'affects impish'
entry as Fix Released.
I also found the commit (here with hash 8f355838f663) in hirsute master.
It landed there based on https://bugs.launchpad.net/bugs/1946788 "Hirsute
update: upstream stable patchset 2021-10-12" and is tagged with
Ubuntu-5.11.0-39.43 (and newer) and since there is 5.11.0.40.41 in
hirsute-updates, the patch is already rolled out for hirsute, hence marking the
'affects hirsute' entry as Fix Released.
And finally I also found the commit (here with hash b8265c7188e4) in focal
master-next.
It landed there based on https://bugs.launchpad.net/bugs/1946024 "Focal update:
v5.4.146 upstream stable release" and is tagged with Ubuntu-5.4.0-90.101 and
since there is 5.4.0.90.94 in focal-updates (btw. the last digit can be
ignored), the patch is already rolled out for focal, hence marking the 'affects
focal' entry as Fix Released, too.
(I like it is fixes were marked for upstream stable updates :-)
** Also affects: linux (Ubuntu Impish)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Jammy)
Importance: Undecided
Assignee: Skipper Bug Screeners (skipper-screen-team)
Status: New
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: ubuntu-z-systems
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Jammy)
Status: New => Fix Released
** Changed in: linux (Ubuntu Impish)
Status: New => Fix Released
** Changed in: linux (Ubuntu Hirsute)
Status: New => Fix Released
** Changed in: linux (Ubuntu Focal)
Status: New => Fix Committed
** Changed in: linux (Ubuntu Focal)
Status: Fix Committed => Fix Released
** Changed in: ubuntu-z-systems
Status: New => Fix Released
--
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/1951109
Title:
[UBUNTU 20.04] kvm: floating interrupts may get stuck
Status in Ubuntu on IBM z Systems:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Focal:
Fix Released
Status in linux source package in Hirsute:
Fix Released
Status in linux source package in Impish:
Fix Released
Status in linux source package in Jammy:
Fix Released
Bug description:
Description: kvm: floating interrupts may get stuck
Symptom: Most prominently guest stuck in IPL.
Problem: When trying to pick an idle cpu to process the
interrupts we can end up messing up, and picking,
for example a stopped vcpu, because we first look
up an index form the kvm->arch.idle_mask and then
use it to obtain a cpu using kvm_get_vcpu() The
trouble is, we made kvm->arch.idle_mask to be
indexed with cpu_id, while kvm_get_vcpu() expects
a vcpu_idx. Hereby vcpu_id is an identifier that
comes from userspace, while vcpu_idx'es are given
away at vcpu creation FCFS. In practice QEMU does
currently the creation of vcpus so that the two
end up having the same value. That is why we did
not notice this problem for years.
Reproduction: Make sure you cpu_id's and cpu_idx'es aren't the
same, and try to IPL a guest.
Solution: Make kvm->arch.idle_mask cpu_idx based.
Upstream-ID: a3e03bc1368c1bc16e19b001fc96dc7430573cc8
Date: 2021-09-09
Author: Halil Pasic <pa...@linux.ibm.com>
Component: kernel
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1951109/+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
