disco/linux: 5.0.0-56.60 -proposed tracker

Bug #1884984 reported by Kleber Sacilotto de Souza
18
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Kernel SRU Workflow
Fix Released
Medium
Unassigned
Automated-testing
Invalid
Medium
Unassigned
Certification-testing
Invalid
Medium
Unassigned
Prepare-package
Fix Released
Medium
Thadeu Lima de Souza Cascardo
Prepare-package-lrm
Fix Released
Medium
Thadeu Lima de Souza Cascardo
Prepare-package-meta
Fix Released
Medium
Thadeu Lima de Souza Cascardo
Prepare-package-signed
Fix Released
Medium
Thadeu Lima de Souza Cascardo
Promote-to-proposed
Invalid
Medium
Ubuntu Stable Release Updates Team
Promote-to-security
Invalid
Medium
Ubuntu Stable Release Updates Team
Promote-to-updates
Invalid
Medium
Ubuntu Stable Release Updates Team
Regression-testing
Invalid
Medium
Unassigned
Security-signoff
Invalid
Medium
Canonical Security Team
Verification-testing
Fix Released
Medium
Canonical Kernel Team
linux (Ubuntu)
Disco
Won't Fix
Medium
Unassigned

Bug Description

This bug will contain status and test results related to a kernel source (or snap) as stated in the title.

For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

-- swm properties --
packages:
  lrm: linux-restricted-modules
  main: linux
  meta: linux-meta
  signed: linux-signed
phase: Complete
phase-changed: Tuesday, 30. June 2020 23:26 UTC
reason: {}
trackers:
  bionic/linux-bluefield: bug 1882722
  bionic/linux-gke-5.0: bug 1882721
  bionic/linux-hwe-5.0: bug 1882718
  bionic/linux-oem-osp1: bug 1884983
variant: debs
versions:
  lrm: 5.0.0-56.60
  main: 5.0.0-56.60
  meta: 5.0.0.56.57
  signed: 5.0.0-56.60

tags: added: kernel-release-tracking-bug-live
description: updated
tags: added: kernel-sru-cycle-2020.06.08-6
description: updated
Changed in kernel-sru-workflow:
status: New → Confirmed
importance: Undecided → Medium
Changed in linux (Ubuntu Disco):
importance: Undecided → Medium
Changed in kernel-sru-workflow:
status: Confirmed → In Progress
description: updated
summary: - disco/linux: <version to be filled> -proposed tracker
+ disco/linux: 5.0.0-56.60 -proposed tracker
description: updated
description: updated
description: updated
description: updated
description: updated
description: updated
description: updated
description: updated
description: updated
description: updated
Revision history for this message
Khaled El Mously (kmously) wrote :

There are no VT bugs for disco. However, I did manually go over the commits that were made to the disco branch.

Besides the linux-stable patches, there are basically 3 CVE fixes, a test-fix, and a hardware-specific fix (#1802691)

All are very low risk.

CVE-2020-0543 UBUNTU/SAUCE: x86/speculation/srbds: do not try to turn mitigation off when not supported
CVE-2020-10711 netlabel: cope with NULL catmap
CVE-2020-13143 USB: gadget: fix illegal array access in binding with UDC

description: updated
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Workflow done!

All tasks have been completed and the bug is being set to Fix Released

Changed in kernel-sru-workflow:
status: In Progress → Fix Released
Steve Langasek (vorlon)
Changed in linux (Ubuntu Disco):
status: New → Won't Fix
tags: removed: kernel-release-tracking-bug-live
Revision history for this message
Ubuntu SRU Bot (ubuntu-sru-bot) wrote : Autopkgtest regression report (linux-hwe-5.0/5.0.0-57.61~18.04.1)

All autopkgtests for the newly accepted linux-hwe-5.0 (5.0.0-57.61~18.04.1) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:

linux-hwe-5.0/5.0.0-57.61~18.04.1 (armhf)

Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-migration/bionic/update_excuses.html#linux-hwe-5.0

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.