bionic/linux-aws: 4.15.0-1055.57 -proposed tracker

Bug #1852270 reported by Stefan Bader on 2019-11-12
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Kernel SRU Workflow
Medium
Unassigned
Automated-testing
Medium
Canonical Kernel Team
Certification-testing
Medium
Canonical Hardware Certification
Prepare-package
Medium
Kleber Sacilotto de Souza
Prepare-package-lrm
Medium
Kleber Sacilotto de Souza
Prepare-package-meta
Medium
Kleber Sacilotto de Souza
Promote-to-proposed
Medium
Łukasz Zemczak
Promote-to-security
Medium
Ubuntu Stable Release Updates Team
Promote-to-updates
Medium
Ubuntu Stable Release Updates Team
Regression-testing
Medium
Canonical Kernel Team
Security-signoff
Medium
Canonical Security Team
Verification-testing
Medium
Canonical Kernel Team
linux-aws (Ubuntu)
Undecided
Unassigned
Bionic
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
kernel-stable-master-bug: 1854027
packages:
  lrm: linux-restricted-modules-aws
  main: linux-aws
  meta: linux-meta-aws
phase: Testing
phase-changed: Tuesday, 19. November 2019 21:16 UTC
proposed-announcement-sent: true
proposed-testing-requested: true
reason:
  regression-testing: Ongoing -- testing in progress
  security-signoff: Stalled -- waiting for signoff
  verification-testing: Ongoing -- testing in progress
trackers:
  bionic/linux-aws-fips: bug 1852268
  bionic/linux-aws/aws-kernel: bug 1852267
  xenial/linux-aws-hwe: bug 1852269
variant: debs

CVE References

Stefan Bader (smb) on 2019-11-12
tags: added: bionic kernel-release-tracking-bug
Changed in linux-aws (Ubuntu Bionic):
status: New → Confirmed
Changed in linux-aws (Ubuntu):
status: New → Invalid
Changed in linux-aws (Ubuntu Bionic):
importance: Undecided → Medium
tags: added: kernel-release-tracking-bug-live
description: updated
tags: added: kernel-sru-cycle-2019.11.11-1
Stefan Bader (smb) on 2019-11-12
description: updated
tags: added: kernel-sru-derivative-of-1852289
Changed in kernel-sru-workflow:
status: New → In Progress
importance: Undecided → Medium
summary: - linux-aws: <version to be filled> -proposed tracker
+ bionic/linux-aws: <version to be filled> -proposed tracker
description: updated
description: updated
summary: - bionic/linux-aws: <version to be filled> -proposed tracker
+ bionic/linux-aws: 4.15.0-1055.57 -proposed tracker
description: updated
description: updated
description: updated
description: updated
description: updated
tags: added: block-proposed-bionic
tags: added: block-proposed
description: updated
description: updated
description: updated
description: updated
description: updated
description: updated
description: updated
description: updated
Stefan Bader (smb) on 2019-11-26
description: updated
tags: removed: kernel-sru-derivative-of-1852289
tags: added: kernel-sru-derivative-of-1854027
tags: removed: kernel-sru-derivative-of-1854027
tags: added: kernel-sru-derivative-of-1854027
Launchpad Janitor (janitor) wrote :
Download full text (31.5 KiB)

This bug was fixed in the package linux-aws - 4.15.0-1056.58

---------------
linux-aws (4.15.0-1056.58) bionic; urgency=medium

  * bionic/linux-aws: 4.15.0-1056.58 -proposed tracker (LP: #1854029)

  [ Ubuntu: 4.15.0-72.81 ]

  * bionic/linux: 4.15.0-72.81 -proposed tracker (LP: #1854027)
  * [Regression] Bionic kernel 4.15.0-71.80 can not boot on ThunderX
    (LP: #1853326)
    - Revert "arm64: Use firmware to detect CPUs that are not affected by
      Spectre-v2"
    - Revert "arm64: Get rid of __smccc_workaround_1_hvc_*"
  * [Regression] Bionic kernel 4.15.0-71.80 can not boot on ThunderX2 and
    Kunpeng920 (LP: #1852723)
    - SAUCE: arm64: capabilities: Move setup_boot_cpu_capabilities() call to
      correct place

linux-aws (4.15.0-1055.57) bionic; urgency=medium

  * bionic/linux-aws: 4.15.0-1055.57 -proposed tracker (LP: #1852270)

  * Bionic update: upstream stable patchset 2019-10-29 (LP: #1850541)
    - [Config] aws: updateconfigs for USB_RIO500

  * ARM CPU support update (LP: #1850675)
    - irqchip/gic-v3-its: Refactor LPI allocator
    - irqchip/gic-v3-its: Use full range of LPIs
    - irqchip/gic-v3-its: Move minimum LPI requirements to individual busses
    - irqchip/gic-v3-its: Drop chunk allocation compatibility
    - irqchip/gic-v3: Expose GICD_TYPER in the rdist structure
    - irqchip/gic-v3-its: Honor hypervisor enforced LPI range
    - irqchip/gic-v3-its: Reduce minimum LPI allocation to 1 for PCI devices
    - irqchip/gic-v3: Allow LPIs to be disabled from the command line
    - irqchip/gic-v3: Ensure GICR_CTLR.EnableLPI=0 is observed before enabling
    - irqchip/gic-v3-its: Cap lpi_id_bits to reduce memory footprint
    - irqchip/gic-v3-its: Change initialization ordering for LPIs
    - irqchip/gic-v3-its: Simplify LPI_PENDBASE_SZ usage
    - irqchip/gic-v3-its: Split property table clearing from allocation
    - irqchip/gic-v3-its: Move pending table allocation to init time
    - irqchip/gic-v3-its: Keep track of property table's PA and VA
    - irqchip/gic-v3-its: Allow use of pre-programmed LPI tables
    - irqchip/gic-v3-its: Use pre-programmed redistributor tables with kdump
      kernels
    - irqchip/gic-v3-its: Check that all RDs have the same property table
    - efi: honour memory reservations passed via a linux specific config table
    - efi: add API to reserve memory persistently across kexec reboot
    - irqchip/gic-v3-its: Register LPI tables with EFI config table
    - irqchip/gic-v3-its: Allow use of LPI tables in reserved memory
    - arm64: kill config_sctlr_el1()
    - arm64: Fix silly typo in comment
    - KVM: arm64: Set SCTLR_EL2.DSSBS if SSBD is forcefully disabled and !vhe
    - arm64: cpu: Move errata and feature enable callbacks closer to callers
    - arm64/cpufeature: Convert hook_lock to raw_spin_lock_t in cpu_enable_ssbs()
    - efi/arm: libstub: add a root memreserve config table
    - efi: Permit calling efi_mem_reserve_persistent() from atomic context
    - efi: Prevent GICv3 WARN() by mapping the memreserve table before first use
    - efi: Permit multiple entries in persistent memreserve data structure
    - arm64: Avoid flush_icache_range() in alternatives patching code

  [ ...

Changed in linux-aws (Ubuntu Bionic):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers