focal/linux-azure: 5.4.0-1038.40 -proposed tracker

Bug #1911317 reported by Kelsey Steele
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Kernel SRU Workflow
Fix Released
Medium
Unassigned
Automated-testing
Fix Released
Medium
Canonical Kernel Team
Certification-testing
Invalid
Medium
Unassigned
Prepare-package
Fix Released
Medium
Khaled El Mously
Prepare-package-lrm
Fix Released
Medium
Khaled El Mously
Prepare-package-meta
Fix Released
Medium
Khaled El Mously
Prepare-package-signed
Fix Released
Medium
Khaled El Mously
Promote-to-proposed
Fix Released
Medium
Andy Whitcroft
Promote-to-security
New
Medium
Ubuntu Stable Release Updates Team
Promote-to-updates
New
Medium
Ubuntu Stable Release Updates Team
Regression-testing
In Progress
Medium
Canonical Kernel Team
Security-signoff
In Progress
Medium
Steve Beattie
Stakeholder-signoff
Confirmed
Medium
linux-azure stakeholder signoff
Verification-testing
In Progress
Medium
Canonical Kernel Team
linux-azure (Ubuntu)
Focal
Fix Released
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 --
boot-testing-requested: true
built:
  lrm: build#1
  main: build#1
  meta: build#1
  signed: build#1
kernel-stable-master-bug: 1911333
packages:
  lrm: linux-restricted-modules-azure
  main: linux-azure
  meta: linux-meta-azure
  signed: linux-signed-azure
phase: Testing
phase-changed: Sunday, 17. January 2021 22:52 UTC
proposed-announcement-sent: true
proposed-testing-requested: true
reason:
  regression-testing: Ongoing -- testing in progress
  security-signoff: Pending -- waiting for signoff
  stakeholder-signoff: Stalled -- waiting for signoff
  verification-testing: Ongoing -- testing in progress
synthetic:
  :promote-to-as-proposed: Fix Released
trackers:
  bionic/linux-azure-5.4: bug 1911316
variant: debs
versions:
  lrm: 5.4.0-1038.40
  main: 5.4.0-1038.40
  meta: 5.4.0.1038.36
  signed: 5.4.0-1038.40

CVE References

tags: added: kernel-release-tracking-bug-live
description: updated
tags: added: kernel-sru-cycle-2021.01.04-3
description: updated
description: updated
tags: added: kernel-sru-derivative-of-1911333
Changed in kernel-sru-workflow:
status: New → Confirmed
importance: Undecided → Medium
Changed in linux-azure (Ubuntu Focal):
importance: Undecided → Medium
Changed in kernel-sru-workflow:
status: Confirmed → In Progress
description: updated
description: updated
description: updated
summary: - focal/linux-azure: <version to be filled> -proposed tracker
+ focal/linux-azure: 5.4.0-1038.40 -proposed tracker
description: updated
description: updated
description: updated
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in linux-azure (Ubuntu Focal):
status: New → Confirmed
description: updated
description: updated
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
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package linux-azure - 5.4.0-1039.41

---------------
linux-azure (5.4.0-1039.41) focal; urgency=medium

  * focal/linux-azure: 5.4.0-1039.41 -proposed tracker (LP: #1912002)

  * Use Azure host for time keeping in all images (LP: #1896784)
    - hv_utils: return error if host timesysnc update is stale
    - hv_utils: drain the timesync packets on onchannelcallback

  * [linux-azure] Batch hibernate and resume IO requests (LP: #1904458)
    - PM: hibernate: Batch hibernate and resume IO requests

linux-azure (5.4.0-1038.40) focal; urgency=medium

  * focal/linux-azure: 5.4.0-1038.40 -proposed tracker (LP: #1911317)

  [ Ubuntu: 5.4.0-63.71 ]

  * focal/linux: 5.4.0-63.71 -proposed tracker (LP: #1911333)
  * overlay: permission regression in 5.4.0-51.56 due to patches related to
    CVE-2020-16120 (LP: #1900141)
    - ovl: do not fail because of O_NOATIME
  * Focal update: v5.4.79 upstream stable release (LP: #1907151)
    - net/mlx5: Use async EQ setup cleanup helpers for multiple EQs
    - net/mlx5: poll cmd EQ in case of command timeout
    - net/mlx5: Fix a race when moving command interface to events mode
    - net/mlx5: Add retry mechanism to the command entry index allocation
  * Kernel 5.4.0-56 Wi-Fi does not connect (LP: #1906770)
    - mt76: fix fix ampdu locking
  * [Ubuntu 21.04 FEAT] mpt3sas: Request to include the patch set which supports
    topology where zoning is enabled in expander (LP: #1899802)
    - scsi: mpt3sas: Define hba_port structure
    - scsi: mpt3sas: Allocate memory for hba_port objects
    - scsi: mpt3sas: Rearrange _scsih_mark_responding_sas_device()
    - scsi: mpt3sas: Update hba_port's sas_address & phy_mask
    - scsi: mpt3sas: Get device objects using sas_address & portID
    - scsi: mpt3sas: Rename transport_del_phy_from_an_existing_port()
    - scsi: mpt3sas: Get sas_device objects using device's rphy
    - scsi: mpt3sas: Update hba_port objects after host reset
    - scsi: mpt3sas: Set valid PhysicalPort in SMPPassThrough
    - scsi: mpt3sas: Handling HBA vSES device
    - scsi: mpt3sas: Add bypass_dirty_port_flag parameter
    - scsi: mpt3sas: Handle vSES vphy object during HBA reset
    - scsi: mpt3sas: Add module parameter multipath_on_hba
    - scsi: mpt3sas: Bump driver version to 35.101.00.00

  [ Ubuntu: 5.4.0-62.70 ]

  * focal/linux: 5.4.0-62.70 -proposed tracker (LP: #1911144)
  * CVE-2020-28374
    - SAUCE: target: fix XCOPY NAA identifier lookup
  * Packaging resync (LP: #1786013)
    - update dkms package versions

 -- Marcelo Henrique Cerri <email address hidden> Mon, 18 Jan 2021 09:44:59 -0300

Changed in linux-azure (Ubuntu Focal):
status: Confirmed → Fix Released
Andy Whitcroft (apw)
tags: removed: kernel-release-tracking-bug-live
Changed in kernel-sru-workflow:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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