linux: 4.4.0-125.150 -proposed tracker

Bug #1770011 reported by Stefan Bader on 2018-05-08
22
This bug affects 2 people
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
Stefan Bader
Prepare-package-meta
Medium
Stefan Bader
Prepare-package-signed
Medium
Stefan Bader
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
Po-Hsu Lin
Security-signoff
Medium
Steve Beattie
Snap-certification-testing
Medium
Canonical Hardware Certification
Snap-release-to-beta
Medium
Canonical Kernel Team
Snap-release-to-candidate
Medium
Canonical Kernel Team
Snap-release-to-edge
Medium
Canonical Kernel Team
Snap-release-to-stable
Medium
Canonical Kernel Team
Upload-to-ppa-dnu
Medium
Unassigned
Verification-testing
Medium
Canonical Kernel Team
linux (Ubuntu)
Undecided
Unassigned
Xenial
Medium
Unassigned

Bug Description

This bug is for tracking the <version to be filled> upload package. This bug will contain status and testing results related to that upload.

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

backports: bug 1770013 (linux-aws), bug 1770015 (linux-lts-xenial)
derivatives: bug 1770016 (linux-aws), bug 1770018 (linux-euclid), bug 1770019 (linux-kvm), bug 1770020 (linux-raspi2), bug 1770023 (linux-snapdragon)
-- swm properties --
boot-testing-requested: true
bugs-spammed: true
phase: Promoted to proposed
proposed-announcement-sent: true
proposed-testing-requested: true

Stefan Bader (smb) on 2018-05-08
tags: added: kernel-release-tracking-bug
tags: added: kernel-release-tracking-bug-live
tags: added: xenial
Changed in linux (Ubuntu Xenial):
status: New → Confirmed
Changed in linux (Ubuntu):
status: New → Invalid
Changed in linux (Ubuntu Xenial):
importance: Undecided → Medium
Changed in kernel-sru-workflow:
status: New → In Progress
importance: Undecided → Medium
tags: added: kernel-sru-cycle-2018.04.23-2
tags: added: kernel-sru-master-kernel
Stefan Bader (smb) on 2018-05-08
description: updated
Stefan Bader (smb) on 2018-05-08
summary: - linux: <version to be filled> -proposed tracker
+ linux: 4.4.0-125.149 -proposed tracker
Brad Figg (brad-figg) on 2018-05-09
description: updated
description: updated
Stefan Bader (smb) on 2018-05-09
summary: - linux: 4.4.0-125.149 -proposed tracker
+ linux: 4.4.0-125.150 -proposed tracker
Brad Figg (brad-figg) on 2018-05-10
tags: added: block-proposed-xenial
tags: added: block-proposed
description: updated
Brad Figg (brad-figg) on 2018-05-10
description: updated
description: updated

Hardware certification has been completed on linux 4.4.0-123.147 (bug 1766604).

Snap beta testing complete, no regressions found. Ready for promotion. Results here: https://trello.com/c/cDGMkVKo/254-pc-kernel-440-125150-118

Po-Hsu Lin (cypressyew) on 2018-05-15
tags: added: certification-testing-passed
tags: added: kernel-block-proposed
Po-Hsu Lin (cypressyew) wrote :

Mark this task as incomplete for the missing i386 tests.

4.4.0-125.150 - lowlatency
Regression test CMPL, RTB.

Issue to note in amd64:
  ubuntu_kvm_unit_tests - 29 failed on amaura, 18 failed on groucho, 20 failed on michael, 28 failed on pepe
  ubuntu_lxc - lxc-test-ubuntu (Failed to start networking in ubuntu-cloud container)
  ubuntu_qrt_kernel_aslr_collisions - network issue, not a bug
  ubuntu_stress_smoke_test - efivar test failed, test has been disabled in the test suite

4.4.0-125.150 - generic
Regression test CMPL, RTB.

Issue to note in amd64:
  ubuntu_kvm_unit_tests - 28 failed on amaura, 20 failed on michael, 28 failed on pepe
  ubuntu_stress_smoke_test - efivar test failed, test has been disabled in the test suite

Issue to note in arm64:
  hwclock - issue for HP m400 (bug 1716603)
  ubuntu_docker_smoke_test - test case issue
  ubuntu_kvm_smoke_test - unable to create KVM with uvtool (bug 1749427)
  ubuntu_kvm_unit_tests - pmu on ms10-34-mcdivittB0-kernel (bug 1751000) gicv2-ipi and gicv2-active on starmie
  ubuntu_stress_smoke_test - efivar test failed, test has been disabled in the test suite

Issue to note in ppc64le:
  ubuntu_kvm_smoke_test - unable to create KVM with uvtool, bug 1755118
  ubuntu_stress_smoke_test - failed on entei, network issue

Issue to note in s390x (Ubuntu on LPAR):
  aio_dio_bugs - invalidate-failure failed (bug 1730895) subblock-eof-read failed (bug 1768430) extend-stat failed (bug 1768435)
  libhugetlbfs - failed 11 killed by signal 7 bad config 1
  scrashme - Test failed to build (bug 1689240)
  ubuntu_bpf_jit - unable to insert test_bpf on Xenial s390x (bug 1768452)
  ubuntu_kvm_smoke_test - uvtool issue (bug 1729854)
  ubuntu_lxc - lxc-test-ubuntu failed (Failed to start networking in ubuntu-cloud container)

Issue to note in s390x (zKVM):
  aio_dio_bugs - invalidate-failure failed (bug 1730895) subblock-eof-read failed (bug 1768430) extend-stat failed (bug 1768435)
  libhugetlbfs - failed 11 killed by signal 7 bad config 1
  scrashme - Test failed to build (bug 1689240)
  ubuntu_bpf_jit - unable to insert test_bpf on Xenial s390x (bug 1768452)
  ubuntu_kvm_smoke_test - uvtool issue (bug 1729854)
  ubuntu_kvm_unit_tests - 11 failed (nested kvm is not supported)

Issue to note in s390x (zVM):
  aio_dio_bugs - invalidate-failure failed (bug 1730895) subblock-eof-read failed (bug 1768430) extend-stat failed (bug 1768435)
  libhugetlbfs - failed 11 killed by signal 7 bad config 1
  scrashme - Test failed to build (bug 1689240)
  ubuntu_bpf_jit - unable to insert test_bpf on Xenial s390x (bug 1768452)
  ubuntu_ecryptfs - passed after re-test
  ubuntu_kvm_smoke_test - uvtool issue (bug 1729854)
  ubuntu_kvm_unit_tests - skey failed

MISSING i386 result in this cycle: curtin bug 1768709

Still missing regression results for i386, setting regression-testing to 'Fix Released' so the release can proceed.

There are a few bugs that haven't been verified yet, however, they are mostly related to fixing hardware issue and have low regression potential. Given that, I'm setting verification-testing to 'Fix Released' so the release can proceed.

Launchpad Janitor (janitor) wrote :
Download full text (59.3 KiB)

This bug was fixed in the package linux - 4.4.0-127.153

---------------
linux (4.4.0-127.153) xenial; urgency=medium

  * CVE-2018-3639 (powerpc)
    - powerpc/pseries: Support firmware disable of RFI flush
    - powerpc/powernv: Support firmware disable of RFI flush
    - powerpc/rfi-flush: Move the logic to avoid a redo into the debugfs code
    - powerpc/rfi-flush: Make it possible to call setup_rfi_flush() again
    - powerpc/rfi-flush: Always enable fallback flush on pseries
    - powerpc/rfi-flush: Differentiate enabled and patched flush types
    - powerpc/rfi-flush: Call setup_rfi_flush() after LPM migration
    - powerpc/pseries: Add new H_GET_CPU_CHARACTERISTICS flags
    - powerpc: Add security feature flags for Spectre/Meltdown
    - powerpc/pseries: Set or clear security feature flags
    - powerpc/powernv: Set or clear security feature flags
    - powerpc/64s: Move cpu_show_meltdown()
    - powerpc/64s: Enhance the information in cpu_show_meltdown()
    - powerpc/powernv: Use the security flags in pnv_setup_rfi_flush()
    - powerpc/pseries: Use the security flags in pseries_setup_rfi_flush()
    - powerpc/64s: Wire up cpu_show_spectre_v1()
    - powerpc/64s: Wire up cpu_show_spectre_v2()
    - powerpc/pseries: Fix clearing of security feature flags
    - powerpc: Move default security feature flags
    - powerpc/pseries: Restore default security feature flags on setup
    - SAUCE: powerpc/64s: Add support for a store forwarding barrier at kernel
      entry/exit

  * CVE-2018-3639 (x86)
    - SAUCE: Clean up IBPB and IBRS control functions and macros
    - SAUCE: Fix up IBPB and IBRS kernel parameters documentation
    - SAUCE: Remove #define X86_FEATURE_PTI
    - x86/cpufeature: Move some of the scattered feature bits to x86_capability
    - x86/cpufeature: Cleanup get_cpu_cap()
    - x86/cpu: Probe CPUID leaf 6 even when cpuid_level == 6
    - x86/cpufeatures: Add CPUID_7_EDX CPUID leaf
    - x86/cpufeatures: Add Intel feature bits for Speculation Control
    - SAUCE: x86/kvm: Expose SPEC_CTRL from the leaf
    - x86/cpufeatures: Add AMD feature bits for Speculation Control
    - x86/msr: Add definitions for new speculation control MSRs
    - SAUCE: x86/msr: Rename MSR spec control feature bits
    - x86/pti: Do not enable PTI on CPUs which are not vulnerable to Meltdown
    - x86/cpufeature: Blacklist SPEC_CTRL/PRED_CMD on early Spectre v2 microcodes
    - x86/speculation: Add basic IBPB (Indirect Branch Prediction Barrier) support
    - x86/speculation: Add <asm/msr-index.h> dependency
    - x86/cpufeatures: Clean up Spectre v2 related CPUID flags
    - x86/cpuid: Fix up "virtual" IBRS/IBPB/STIBP feature bits on Intel
    - SAUCE: x86/speculation: Move vendor specific IBRS/IBPB control code
    - SAUCE: x86: Add alternative_msr_write
    - SAUCE: x86/nospec: Simplify alternative_msr_write()
    - SAUCE: x86/bugs: Concentrate bug detection into a separate function
    - SAUCE: x86/bugs: Concentrate bug reporting into a separate function
    - arch: Introduce post-init read-only memory
    - SAUCE: x86/bugs: Read SPEC_CTRL MSR during boot and re-use reserved bits
    - SAUCE: x86/bugs, KVM: Support the combination of guest a...

Changed in linux (Ubuntu Xenial):
status: Confirmed → Fix Released

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

Changed in kernel-sru-workflow:
status: In Progress → Fix Released
tags: removed: kernel-release-tracking-bug-live
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers