** Changed in: ubuntu-z-systems
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1953338
Title:
[UBUNTU 20.04] KVM hardware diagnose data improvements for
This bug was fixed in the package qemu - 1:4.2-3ubuntu6.21
---
qemu (1:4.2-3ubuntu6.21) focal-security; urgency=medium
* SECURITY UPDATE: crash or code exec in USB redirector device emulation
- debian/patches/CVE-2021-3682.patch: fix free call in
hw/usb/redirect.c.
-
There was an issue with our builders yesterday,
restarting the same build today worked again - package is now there (at the
PPA).
I did a quick test (since I had the env. still from the LP#1953334 verification.
And from what I understood it seems to be fine:$ sudo grep "cpnc to 4"
** Changed in: ubuntu-z-systems
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1953338
Title:
[UBUNTU 20.04] KVM hardware diagnose data improvements for
The block-proposed tags are release specific so I've added block-
proposed-focal.
** Tags added: block-proposed-focal
** Changed in: qemu (Ubuntu Focal)
Status: In Progress => Fix Committed
** Tags added: verification-needed verification-needed-focal
--
You received this bug
** Changed in: ubuntu-z-systems
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1953338
Title:
[UBUNTU 20.04] KVM hardware diagnose data improvements for guest
** Description changed:
SRU Justification:
==
[Impact]
* Hardware diagnose data (diag 318) of KVM guest kernel cannot be
handled.
* A fix is needed to enhance problem determination of guest kernel under
KVM using DIAG 0x318 instruction execution.
* The
** Changed in: qemu (Ubuntu Focal)
Status: Incomplete => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1953338
Title:
[UBUNTU 20.04] KVM hardware diagnose data improvements for
Uploaded to focal-unapproved
** Tags added: block-proposed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1953338
Title:
[UBUNTU 20.04] KVM hardware diagnose data improvements for guest
kernel -
** Description changed:
+ SRU Justification:
+ ==
+
+ [Impact]
+
+ * Hardware diagnose data (diag 318) of KVM guest kernel cannot be
+ handled.
+
+ * A fix is needed to enhance problem determination of guest kernel under
+ KVM using DIAG 0x318 instruction execution.
+
+ * The
FYI - right now I have nothing else in the SRU queue for qemu.
The plan to handle this upload without being a "useless" download for any
non-s390x users will be that we drive the SRU normally but set block-proposed.
There it will be picked up by a subsequent qemu security update in not too much
Thank you for the backported patches,
With those I've created a test PPA for Focal at [1] (still building atm).
@Frank AFAIK you need that to test the current proposed kernel.
Once you can confirm me that this looks good we can prep and kick off the SRU
process of this upload here as well.
[1]:
Incomplete since we wait for the proper rebase for the backports as I
asked in early December.
** Changed in: qemu (Ubuntu Focal)
Status: Triaged => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: ubuntu-z-systems
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1953338
Title:
[UBUNTU 20.04] KVM hardware diagnose data improvements for guest
kernel
Note: this is related to bug https://bugs.launchpad.net/bugs/1953334
It shares the motivation and the test steps.
Both fixes can exists along (no hard version requirement needed in he uploads)
but only when both are together it can fully work.
--
You received this bug notification because you
They might be backported to plain 4.2, but they do not apply cleanly to
1:4.2-3ubuntu6.19.
0001 & 0002:
The patch directly from upstream git applies, but your backport does not - so I
just used cherry picks
0003:
Neither your backprt nor a cherry pick worked as-is.
Here things start to be
Thanks for the provided backports.
So far I was assuming this is a new feat for Jammy, but now no more.
Maybe we need to talk about what the target of this bug is - is it Focal and
therefore the backport target here was 4.2 :-)
backport/origin upstream-hash patch
B 912d70d2
I've made some patched test kernel available here:
https://launchpad.net/~fheimes/+archive/ubuntu/lp1953334
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1953338
Title:
[UBUNTU 20.04] KVM hardware
** Changed in: qemu (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1953338
Title:
[UBUNTU 20.04] KVM hardware diagnose data improvements for guest
kernel
Thanks for the heads up,
Please let us know when the upstream discussion settled and there is a commit
id we shall import.
Furthermore as usual if this shall go to older active releases I wanted
to ask from your dev/testing what the best way to trigger/fake diag 318
for testing would be?
**
** Package changed: linux (Ubuntu) => qemu (Ubuntu)
** Also affects: ubuntu-z-systems
Importance: Undecided
Status: New
** Changed in: ubuntu-z-systems
Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team)
** Changed in: qemu (Ubuntu)
Assignee: Skipper Bug
21 matches
Mail list logo
