This bug was fixed in the package linux - 5.4.0-56.62
---
linux (5.4.0-56.62) focal; urgency=medium
* focal/linux: 5.4.0-56.62 -proposed tracker (LP: #1905300)
* CVE-2020-4788
- selftests/powerpc: rfi_flush: disable entry flush if present
- powerpc/64s: flush L1D on
Performing verification for Focal.
I created a i3.large instance on AWS, since it has 1x NVMe drive that
supports trim and block discard.
I ensured that I could reproduce the problem with 5.4.0-54-generic from
-updates, and I followed the instructions in the Testcase section, and
the final
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-
focal' to 'verification-done-focal'. If the problem still exists, change
the tag
This bug was fixed in the package linux-azure - 5.4.0-1031.32
---
linux-azure (5.4.0-1031.32) focal; urgency=medium
[ Ubuntu: 5.4.0-51.56 ]
* Packaging resync (LP: #1786013)
- update dkms package versions
linux-azure (5.4.0-1030.31) focal; urgency=medium
[ Ubuntu:
** Changed in: linux (Ubuntu Focal)
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/1896154
Title:
btrfs: trimming a btrfs device which has been shrunk
** Changed in: linux-azure (Ubuntu Focal)
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/1896154
Title:
btrfs: trimming a btrfs device which has been
We are adding this fix earlier to focal:linux-azure since we are
preparing a re-spin. focal:linux should receive the fix in the next SRU
cycle.
** Also affects: linux-azure (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-azure (Ubuntu Focal)
Status: New => In
