For reference, the issue with the now backported patch was identified
upstream (https://lkml.org/lkml/2020/9/30/352), and the following patch
resolves it:
commit 0891fb39ba67bd7ae023ea0d367297010781
Author: Juergen Gross
Date: Wed Sep 30 11:16:14 2020 +0200
xen/events: don't use
This bug was fixed in the package linux - 4.4.0-193.224
---
linux (4.4.0-193.224) xenial; urgency=medium
* CVE-2020-16119
- SAUCE: dccp: avoid double free of ccid on child socket
linux (4.4.0-192.222) xenial; urgency=medium
* xenial/linux: 4.4.0-192.222 -proposed tracker
Verified on T-aws 4.4.0-1080.84 as well.
** Changed in: ubuntu-kernel-tests
Status: Confirmed => 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/1896725
Title:
Hi Ian and Matthew,
I was installed 4.4.0-1116-aws, machine was boot successfully and I was
able to ssh.
Thanks again
--
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/1896725
Title:
Verifying for xenial:
I enabled -proposed, and installed 4.4.0-1116-aws:
$ uname -rv
4.4.0-1116-aws #129-Ubuntu SMP Tue Sep 29 18:17:22 UTC 2020
I rebooted, and was able to ssh in, and dmesg was clean.
I then installed 4.4.0-192-generic:
$ uname -rv
4.4.0-192-generic #222-Ubuntu SMP Tue Sep
Hi Shay,
We are working to get verification testing completed, would you be able
to confirm this issue is resolved in Xenial 4.4.0-192.222?
Thanks,
Ian
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag
For now we are going with reverting the Xen change that introduced the
regression with 4.4 kernels.
** Changed in: linux (Ubuntu Xenial)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
** Changed in: linux (Ubuntu Xenial)
Status: Confirmed => 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/1896725
Title:
xenial 4.4.0-191-generic in -proposed has a
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
--
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/1896725
Title:
xenial 4.4.0-191-generic in -proposed has a regression
Just to clarify, When reverting one version back to 4.4.0-1114-aws,
no panic was found and instances boot successfully
--
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/1896725
Title:
Or maybe that is not quite the change... I missed that the loop
following, still would be using an anchor taken from the chip data...
--
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/1896725
It looks like being a lucky "side-effect" of
commit 90ad9e2d91067983f3328e21b306323877e5f48a
Author: Thomas Gleixner
Date: Wed Sep 13 23:29:49 2017 +0200
x86/io_apic: Reevaluate vector configuration on activate()
This changes factors out the code that accesses the chip data, but at
the
mp_irqdomain_activate from arch/x86/kernel/apic/io_apic.c will use the
chip_data that is set by the commit referred by Stefan ("XEN uses
irqdesc::irq_data_common::handler_data to store a per interrupt XEN data
pointer which contains XEN specific information.").
>From
So I can confirm the behavior with a local Xen Server and a HVM Xenial
guest. While the current proposed 4.4 kernel crashes while setting up
the acpi interrupt, this does not happen with a 4.15 kernel from
proposed on a Bionic HVM guest. Still I was able to get the 4.4 kernel
to boot by reverting
** Changed in: linux (Ubuntu Xenial)
Assignee: (unassigned) => Stefan Bader (smb)
--
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/1896725
Title:
xenial 4.4.0-191-generic in
Just some additional data without any final conclusion. Talking to Sean,
the affected instance type seem to be all Xen based. The provided
stacktrace backs this. In the past that could have been a mix of
paravirtualized (PV) and hardware virtualized (HVM). But since
spectre/meltdown I expect that
Testing picked this up a few hours before the bug was open, looks like
its affecting quite a few instances as mentioned in comment #4. Marking
Confirmed, tagging appropriately.
** Also affects: ubuntu-kernel-tests
Importance: Undecided
Status: New
** Changed in: ubuntu-kernel-tests
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux (Ubuntu Xenial)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I can see this issue on our AWS test pool as well (instances c3.xlarge,
c4.large, m3.large, m4.large, r3.large, t2.small, x1e.xlarge failed with
deployment for 4.4.0-1115-aws)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
Hello @shaynagar, thank you very much for reporting! We will look into
this asap.
More details: 4.4.0-190-generic is fine, 4.4.0-191-generic contains the
regression.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
21 matches
Mail list logo
