** Changed in: linux (Ubuntu)
Status: Fix Committed => Fix Released
** No longer affects: linux (Ubuntu Disco)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1869948
Title:
Multiple Kexec in
** Changed in: linux (Ubuntu Focal)
Status: Fix Committed => Fix Released
** Changed in: linux (Ubuntu Disco)
Importance: Medium => Low
** Changed in: linux (Ubuntu Disco)
Status: Opinion => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs
This bug was fixed in the package linux - 4.4.0-178.208
---
linux (4.4.0-178.208) xenial; urgency=medium
* xenial/linux: 4.4.0-178.208 -proposed tracker (LP: #1870660)
* CVE-2019-19768
- blktrace: Protect q->blk_trace with RCU
- blktrace: fix dereference after null check
This bug was fixed in the package linux - 5.3.0-51.44
---
linux (5.3.0-51.44) eoan; urgency=medium
* CVE-2020-11884
- SAUCE: s390/mm: fix page table upgrade vs 2ndary address mode accesses
-- Thadeu Lima de Souza Cascardo Wed, 22 Apr
2020 17:35:41 -0300
** Changed in: linux
This bug was fixed in the package linux - 4.15.0-99.100
---
linux (4.15.0-99.100) bionic; urgency=medium
* CVE-2020-11884
- SAUCE: s390/mm: fix page table upgrade vs 2ndary address mode accesses
-- Marcelo Henrique Cerri Wed, 22 Apr
2020 15:31:14 -0300
--
You received this
I've verified this LP using AWS instances, so the kernel versions I
tested were -aws flavored; this was necessary given the patch proposed
here is related to the ena driver, which manages an AWS exclusive
virtual NIC.
The versions tested were:
4.4.0.1105 xenial-updates
4.4.0.1106 xenial-proposed
Regarding Disco, despite the "Fix Committed" status I didn't find the
patch in the latest tags from generic tree (Ubuntu-5.0.0-46.50) nor AWS
tree (Ubuntu-aws-5.0.0-1024.27), so I think the patch wasn't merged
(which is not a big deal, given Bionic HWE is now based on 5.3).
I've reverted the "Fix
** Changed in: linux (Ubuntu Disco)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Disco)
Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.lau
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-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verifica
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 'verifica
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-
eoan' to 'verification-done-eoan'. If the problem still exists, change
the tag 'verification
** Also affects: linux (Ubuntu Disco)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Disco)
Status: New => 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/
Even though the proposed patch wasn't applied to Focal, based on Seth's
comment it did make its way to Focal via upstream-stable. Therefore,
marking Focal as fix-released as well.
** Changed in: linux (Ubuntu Xenial)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Bionic)
Comment #5 should have said "marking Focal as fix-committed as well"
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1869948
Title:
Multiple Kexec in AWS Nitro instances fail
To manage notifications
SRU request submitted to kernel team mailing list:
https://lists.ubuntu.com/archives/kernel-team/2020-April/108684.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1869948
Title:
Multiple Kexec in
** Description changed:
- Placeholder
- To be improved
+ [Impact]
+ * Currently, users cannot perform multiple kernel kexec loads on AWS Nitro
instances (KVM-based); after the 2nd or 3rd kexec, an initrd corruption is
observed, with the following signature:
+
+ Initramfs unpacking failed: junk
After debugging the problem, a potential workaround was found which
alleviates but doesn't fix the issue; the workaround is to use the
"retain_initrd" on kexec boots to prevent kernel from freeing the initrd
memory area. Also, it was observed that bigger initrds tend to show the
problem more consis
Testing multiple kexecs usually requires either using two machines (one
triggering ssh commands to the other, which will kexec) or if in one
machine only, cron scripts could be used. The latter approach was the
choice here to validate this Launchpad, by adding the following entry in
crontab:
"@reb
An initrd corruption in AWS Nitro (KVM-based) instances was reported
when trying multiple kexecs sequentially - it usually manifests after
the 2nd or 3rd kexec. By using pstore/ramoops, we collected the attached
log.
** Attachment added: "dmesg.ramoops"
https://bugs.launchpad.net/ubuntu/+sourc
19 matches
Mail list logo
