linux-lts-xenial: 4.4.0-128.154~14.04.1 -proposed tracker

Bug #1772962 reported by Stefan Bader
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
Fix Released
Medium
Taihsiang Ho
Prepare-package
Fix Released
Medium
Stefan Bader
Prepare-package-meta
Fix Released
Medium
Stefan Bader
Prepare-package-signed
Fix Released
Medium
Stefan Bader
Promote-to-proposed
Fix Released
Medium
Łukasz Zemczak
Promote-to-security
Fix Released
Medium
Łukasz Zemczak
Promote-to-updates
Fix Released
Medium
Łukasz Zemczak
Regression-testing
Fix Released
Medium
Po-Hsu Lin
Security-signoff
Fix Released
Medium
Steve Beattie
Upload-to-ppa
Invalid
Medium
Canonical Kernel Team
Verification-testing
Fix Released
Medium
Canonical Kernel Team
linux-lts-xenial (Ubuntu)
Invalid
Undecided
Unassigned
Trusty
Fix Released
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
-- swm properties --
boot-testing-requested: true
kernel-stable-master-bug: 1772960
phase: Released
proposed-announcement-sent: true
proposed-testing-requested: true

Stefan Bader (smb)
tags: added: kernel-release-tracking-bug
tags: added: kernel-release-tracking-bug-live
tags: added: trusty
Changed in linux-lts-xenial (Ubuntu Trusty):
status: New → Confirmed
Changed in linux-lts-xenial (Ubuntu):
status: New → Invalid
Changed in linux-lts-xenial (Ubuntu Trusty):
importance: Undecided → Medium
Changed in kernel-sru-workflow:
status: New → In Progress
importance: Undecided → Medium
tags: added: kernel-sru-cycle-2018.05.21-1
tags: added: kernel-sru-backport-of-1772960
Stefan Bader (smb)
summary: - linux-lts-xenial: <version to be filled> -proposed tracker
+ linux-lts-xenial: 4.4.0-128.154~14.04.1 -proposed tracker
Brad Figg (brad-figg)
description: updated
description: updated
Brad Figg (brad-figg)
tags: added: block-proposed-trusty
tags: added: block-proposed
description: updated
Brad Figg (brad-figg)
description: updated
description: updated
Revision history for this message
Po-Hsu Lin (cypressyew) wrote :

4.4.0-128.154~14.04.1 - generic
Regression test CMPL, RTB.

Issue to note in amd64:
  ubuntu_ecryptfs - extend-file-random.sh.btrfs (bug 1684788) trunc-file.sh.btrfs (bug 1684789)
  ubuntu_kvm_smoke_test - uvt-kvm wait issue on Trusty (bug 1732883)
  ubuntu_kvm_unit_tests - 26 failed on pepe

Issue to note in arm64:
  hwclock - issue for HP m400 (bug 1716603)
  ubuntu_cts_kernel - lp1262692 failed, bug for iproute2 (bug 1715376)
  ubuntu_ecryptfs - extend-file-random.sh.btrfs (bug 1684788) trunc-file.sh.btrfs (bug 1684789)
  ubuntu_kvm_smoke_test - unable to create KVM with uvtool (bug 1749427)
  ubuntu_lxc - passed after re-test
  ubuntu_qrt_apparmor - test_old_trusty_regression_testsuite failed to build (bug 1699987)
  ubuntu_qrt_kernel_security - 050 failed (bug 1684776)

Issue to note in i386:
  ubuntu_ecryptfs - extend-file-random.sh.btrfs (bug 1684788) trunc-file.sh.btrfs (bug 1684789)
  ubuntu_kvm_smoke_test - uvt-kvm wait issue on Trusty (bug 1732883)
  ubuntu_kvm_unit_tests - 25 failed on pepe
  ubuntu_ltp_syscalls - fcntl35 / fcntl35_64 in LTP syscall test failed with X-LTS kernel (bug 1774394) fcntl36 in LTP syscall test failed with X-LTS kernel (bug 1774396) inotify07 and inotify08 in LTP syscall test failed with X-LTS kernel (bug 1774387)

Issue to note in ppc64le:
  ubuntu_cts_kernel - lp1262692 failed, bug for iproute2 (bug 1715376)
  ubuntu_kvm_smoke_test - uvtool issue (bug 1729854)
  ubuntu_lxc - no Trusty ppc64le cloud image (bug 1774345)

tags: added: regression-testing-passed
Revision history for this message
Taihsiang Ho (tai271828) wrote :

Hardware Certification have begun testing this -proposed kernel.

Revision history for this message
Taihsiang Ho (tai271828) wrote :

Hardware Certification have completed testing this -proposed kernel. No regressions were observed, results are available here: http://people.canonical.com/~hwcert/sru-testing/trusty/4.4.0-128.154~14.04.1/trusty-4.4-proposed-published.html

tags: added: certification-testing-passed
Brad Figg (brad-figg)
tags: removed: block-proposed-trusty
tags: removed: block-proposed
Revision history for this message
Launchpad Janitor (janitor) wrote :
Download full text (15.2 KiB)

This bug was fixed in the package linux-lts-xenial - 4.4.0-128.154~14.04.1

---------------
linux-lts-xenial (4.4.0-128.154~14.04.1) trusty; urgency=medium

  * linux-lts-xenial: 4.4.0-128.154~14.04.1 -proposed tracker (LP: #1772962)

  * linux: 4.4.0-128.154 -proposed tracker (LP: #1772960)

  * CVE-2018-3639 (x86)
    - x86/cpu: Make alternative_msr_write work for 32-bit code
    - x86/bugs: Fix the parameters alignment and missing void
    - KVM: SVM: Move spec control call after restore of GS
    - x86/speculation: Use synthetic bits for IBRS/IBPB/STIBP
    - x86/cpufeatures: Disentangle MSR_SPEC_CTRL enumeration from IBRS
    - x86/cpufeatures: Disentangle SSBD enumeration
    - x86/cpu/AMD: Fix erratum 1076 (CPB bit)
    - x86/cpufeatures: Add FEATURE_ZEN
    - x86/speculation: Handle HT correctly on AMD
    - x86/bugs, KVM: Extend speculation control for VIRT_SPEC_CTRL
    - x86/speculation: Add virtualized speculative store bypass disable support
    - x86/speculation: Rework speculative_store_bypass_update()
    - x86/bugs: Unify x86_spec_ctrl_{set_guest,restore_host}
    - x86/bugs: Expose x86_spec_ctrl_base directly
    - x86/bugs: Remove x86_spec_ctrl_set()
    - x86/bugs: Rework spec_ctrl base and mask logic
    - x86/speculation, KVM: Implement support for VIRT_SPEC_CTRL/LS_CFG
    - KVM: SVM: Implement VIRT_SPEC_CTRL support for SSBD
    - x86/bugs: Rename SSBD_NO to SSB_NO
    - KVM: VMX: Expose SSBD properly to guests.

  * [i915_bpo] Fix flickering issue after panel change (LP: #1770565)
    - drm/i915: Fix iboost setting for DDI with 4 lanes on SKL
    - drm/i915: Name the "iboost bit"
    - drm/i915: Program iboost settings for HDMI/DVI on SKL
    - drm/i915: Move bxt_ddi_vswing_sequence() call into intel_ddi_pre_enable()
      for HDMI
    - drm/i915: Explicitly use ddi buf trans entry 9 for hdmi
    - drm/i915: Split DP/eDP/FDI and HDMI/DVI DDI buffer programming apart
    - drm/i915: Get the iboost setting based on the port type
    - drm/i915: Simplify intel_ddi_get_encoder_port()
    - drm/i915: Fix iboost setting for SKL Y/U DP DDI buffer translation entry 2
    - drm/i915: KBL - Recommended buffer translation programming for DisplayPort
    - drm/i915: Ignore OpRegion panel type except on select machines

  * [SRU][Bionic/Artful] fix false positives in W+X checking (LP: #1769696)
    - init: fix false positives in W+X checking

  * [Ubuntu 16.04] kernel: fix rwlock implementation (LP: #1761674)
    - SAUCE: (no-up) s390: fix rwlock implementation

  * linux < 4.11: unable to use netfilter logging from non-init namespaces
    (LP: #1766573)
    - netfilter: allow logging from non-init namespaces

  * [LTC Test] Ubuntu 18.04: tm_sigreturn failed on P8 compat mode 16.04.04
    guest (LP: #1771439)
    - powerpc: signals: Discard transaction state from signal frames

  * QCA9377 requires more IRAM banks for its new firmware (LP: #1748345)
    - ath10k: update the IRAM bank number for QCA9377

  * i915/kbl_dmc_ver1.bin failed with error -2 package 1.157.17 kernel
    4.4.0-116-generic (LP: #1752536)
    - ubuntu: i915_bpo - Add MODULE_FIRMWARE for Geminilake's DMC

  * Xenial update to 4.4.131 stable release (LP: #17688...

Changed in linux-lts-xenial (Ubuntu Trusty):
status: Confirmed → Fix Released
Revision history for this message
Brad Figg (brad-figg) wrote : Package Released!

The package has been published and the bug is being set to Fix Released

Changed in kernel-sru-workflow:
status: In Progress → Fix Released
description: updated
description: updated
tags: removed: kernel-release-tracking-bug-live
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.