bionic/linux-gke-5.0: 5.0.0-1024.24~18.04.1 -proposed tracker

Bug #1848994 reported by Khaled El Mously on 2019-10-21
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
Khaled El Mously
Prepare-package-meta
Medium
Khaled El Mously
Prepare-package-signed
Medium
Khaled El Mously
Promote-to-proposed
Medium
Andy Whitcroft
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
Steve Beattie
Verification-testing
Medium
Canonical Kernel Team
linux-gke-5.0 (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
packages:
  main: linux-gke-5.0
  meta: linux-meta-gke-5.0
  signed: linux-signed-gke-5.0
phase: Holding before Promote to Updates
phase-changed: Monday, 11. November 2019 16:55 UTC
proposed-announcement-sent: true
proposed-testing-requested: true
trackers:
  bionic/linux-gke-5.0/gke-kernel: bug 1848993
variant: debs

tags: added: bionic kernel-release-tracking-bug
Changed in linux-gke-5.0 (Ubuntu Bionic):
status: New → Confirmed
Changed in linux-gke-5.0 (Ubuntu):
status: New → Invalid
Changed in linux-gke-5.0 (Ubuntu Bionic):
importance: Undecided → Medium
tags: added: kernel-release-tracking-bug-live
description: updated
tags: added: kernel-sru-cycle-2019.10.21-1
description: updated
tags: added: kernel-sru-backport-of-1848995
Changed in kernel-sru-workflow:
status: New → In Progress
importance: Undecided → Medium
tags: removed: kernel-sru-backport-of-1848995
tags: added: kernel-sru-backport-of-1848995
summary: - linux-gke-5.0: <version to be filled> -proposed tracker
+ bionic/linux-gke-5.0: <version to be filled> -proposed tracker
description: updated
description: updated
summary: - bionic/linux-gke-5.0: <version to be filled> -proposed tracker
+ bionic/linux-gke-5.0: 5.0.0-1024.24~18.04.1 -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
Andy Whitcroft (apw) wrote :

The diff for this seems to show the following emergency commit being lost:

-linux-gke-5.0 (5.0.0-1022.22~18.04.3) bionic; urgency=medium
-
- * bionic/linux-gke-5.0: 5.0.0-1022.22~18.04.3 -proposed tracker (LP: #1847644)
-
- * fdatasync performance regression on 5.0 kernels (LP: #1847641)
- - blk-wbt: fix performance regression in wbt scale_up/scale_down
-
- -- Khalid Elmously <email address hidden> Thu, 10 Oct 2019 14:25:06 -0400

I suspect this has occured because this rebase was not done from the correct tag.

Now I am not 100% convinced we have lost the actual change, bit it would be good confirm that please. If this is present just that the changelog is missformed then we can move this back to Confirmed and accept it, assuming we get the changelog fragment restored for the next upload.

Khaled El Mously (kmously) wrote :

@Andy That change was not lost, it is now known as

b6c15098fa292 blk-wbt: fix performance regression in wbt scale_up/scale_down

and is part of the parent kernel Ubuntu-gcp-5.0.0-1024.24

I will change the status back to confirmed as you suggested, and I have a note ForNextCycle to fix the changelog. I'm not exactly sure how to do that, but I can figure it out then.

Khaled El Mously (kmously) wrote :

Changed the 'promoted-to-proposed' status back to confirmed, as per previous comment.

description: updated
description: updated
description: updated
description: updated
description: updated
description: updated
description: updated
description: updated
Sean Feole (sfeole) on 2019-10-30
tags: added: regression-testing-passed
description: updated
description: updated
description: updated
description: updated
description: updated
Launchpad Janitor (janitor) wrote :
Download full text (39.2 KiB)

This bug was fixed in the package linux-gke-5.0 - 5.0.0-1025.26~18.04.1

---------------
linux-gke-5.0 (5.0.0-1025.26~18.04.1) bionic; urgency=medium

  [ Ubuntu: 5.0.0-1025.26 ]

  * CVE-2019-11135
    - [Config] gcp: Disable TSX by default when possible
  * [REGRESSION] md/raid0: cannot assemble multi-zone RAID0 with default_layout
    setting (LP: #1849682)
    - SAUCE: Fix revert "md/raid0: avoid RAID0 data corruption due to layout
      confusion."
  * refcount underflow and type confusion in shiftfs (LP: #1850867) // CVE-2019-15793
    - SAUCE: shiftfs: Correct id translation for lower fs operations
    - SAUCE: shiftfs: prevent type confusion
    - SAUCE: shiftfs: Fix refcount underflow in btrfs ioctl handling
  * CVE-2018-12207
    - kvm: Convert kvm_lock to a mutex
    - kvm: x86: Do not release the page inside mmu_set_spte()
    - KVM: x86: make FNAME(fetch) and __direct_map more similar
    - KVM: x86: remove now unneeded hugepage gfn adjustment
    - KVM: x86: change kvm_mmu_page_get_gfn BUG_ON to WARN_ON
    - KVM: x86: add tracepoints around __direct_map and FNAME(fetch)
    - kvm: x86, powerpc: do not allow clearing largepages debugfs entry
    - SAUCE: KVM: vmx, svm: always run with EFER.NXE=1 when shadow paging is
      active
    - SAUCE: x86: Add ITLB_MULTIHIT bug infrastructure
    - SAUCE: kvm: mmu: ITLB_MULTIHIT mitigation
    - SAUCE: kvm: Add helper function for creating VM worker threads
    - SAUCE: kvm: x86: mmu: Recovery of shattered NX large pages
    - SAUCE: cpu/speculation: Uninline and export CPU mitigations helpers
    - SAUCE: kvm: x86: mmu: Apply global mitigations knob to ITLB_MULTIHIT
  * CVE-2019-11135
    - KVM: x86: use Intel speculation bugs and features as derived in generic x86
      code
    - x86/msr: Add the IA32_TSX_CTRL MSR
    - x86/cpu: Add a helper function x86_read_arch_cap_msr()
    - x86/cpu: Add a "tsx=" cmdline option with TSX disabled by default
    - x86/speculation/taa: Add mitigation for TSX Async Abort
    - x86/speculation/taa: Add sysfs reporting for TSX Async Abort
    - kvm/x86: Export MDS_NO=0 to guests when TSX is enabled
    - x86/tsx: Add "auto" option to the tsx= cmdline parameter
    - x86/speculation/taa: Add documentation for TSX Async Abort
    - x86/tsx: Add config options to set tsx=on|off|auto
    - SAUCE: x86/speculation/taa: Call tsx_init()
    - [Config] Disable TSX by default when possible
  * CVE-2019-0154
    - SAUCE: drm/i915: Lower RM timeout to avoid DSI hard hangs
    - SAUCE: drm/i915/gen8+: Add RC6 CTX corruption WA
  * CVE-2019-0155
    - SAUCE: drm/i915: Rename gen7 cmdparser tables
    - SAUCE: drm/i915: Disable Secure Batches for gen6+
    - SAUCE: drm/i915: Remove Master tables from cmdparser
    - SAUCE: drm/i915: Add support for mandatory cmdparsing
    - SAUCE: drm/i915: Support ro ppgtt mapped cmdparser shadow buffers
    - SAUCE: drm/i915: Allow parsing of unsized batches
    - SAUCE: drm/i915: Add gen9 BCS cmdparsing
    - SAUCE: drm/i915/cmdparser: Use explicit goto for error paths
    - SAUCE: drm/i915/cmdparser: Add support for backward jumps
    - SAUCE: drm/i915/cmdparser: Ignore Length operands during command matching
  * disco/linux: <...

Changed in linux-gke-5.0 (Ubuntu Bionic):
status: Confirmed → Fix Released
Andy Whitcroft (apw) on 2019-11-13
tags: removed: kernel-sru-backport-of-1848995
description: updated
tags: removed: kernel-release-tracking-bug-live
Changed in kernel-sru-workflow:
status: In Progress → Invalid
Changed in linux-gke-5.0 (Ubuntu Bionic):
status: Fix Released → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers