linux: 4.4.0-141.167 -proposed tracker

[Kleber Sacilotto de Souza]

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 1806570 (linux-aws), bug 1806572 (linux-lts-xenial)
derivatives: bug 1806573 (linux-aws), bug 1806575 (linux-euclid), bug 1806578 (linux-kvm), bug 1806579 (linux-raspi2), bug 1806580 (linux-snapdragon)
-- swm properties --
boot-testing-requested: true
bugs-spammed: true
phase: Released
phase-changed: Friday, 21. December 2018 04:32 UTC
proposed-announcement-sent: true
proposed-testing-requested: true
reason:
  promote-to-updates: Stalled -- snap-release-to-stable is neither "Fix Released"
    nor "Invalid" (Confirmed)

[Devices Certification Bot (ce-certification-qa)]

Snap beta testing complete, no regressions found. Ready for promotion. Results here: https://trello.com/c/DcJMMx1S/542-pc-kernel-440-141167-176

[Taihsiang Ho (tai271828)]

Hardware Certification have begun testing this -proposed kernel.

[Po-Hsu Lin (cypressyew)]

The ecryptfs test is constantly failing on kernel01.
Might be a disk space issue, put this on hold.

[Po-Hsu Lin (cypressyew)]

ecryptfs passed on s390x zVM (kernel01), issue caused by insufficient disk space.
Make this green again.

[Po-Hsu Lin (cypressyew)]

4.4.0-141.167 - lowlatency
Regression test CMPL, RTB.

44 / 52 tests were run, missing: ubuntu_bpf_jit, ubuntu_cts_kernel, ubuntu_cve_kernel, ubuntu_ecryptfs, ubuntu_ltp_syscalls, ubuntu_zfs_fstest, ubuntu_zfs_xfs_generic, xfstests
Issue to note in amd64:
  libhugetlbfs - failed 1 killed by signal 1 bad config 3
  ubuntu_kvm_unit_tests - 30 failed on KVM nodes

4.4.0-141.167 - generic
Regression test CMPL, RTB.

Issue to note in amd64:
  monotonic_time - tsc failed on gonzo
  ubuntu_kvm_unit_tests - 32 failed on amaura, 31 failed on pepe, 30 failed on KVM nodes
  ubuntu_ltp_syscalls - inotify07 (bug 1774387) inotify08 (bug 1775784) fanotify07/fanotify08 timeouted (bug 1775165) fanotify09 timeouted (bug 1775153) fanotify10 (bug 1802454) fanotify11 timeouted (bug 1808107)
  xfstests - xfs xfs/438 timed out

Issue to note in arm64:
  hwclock - issue for HP m400 (bug 1716603)
  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_ltp_syscalls - inotify07 (bug 1774387) inotify08 (bug 1775784) fanotify07/fanotify08 timeouted (bug 1775165) fanotify09 timeouted (bug 1775153) fanotify10 (bug 1802454) fanotify11 timeouted (bug 1808107)
  xfstests - xfs xfs/438 timed out

Issue to note in i386:
  ubuntu_kvm_unit_tests - unable to build on X/T i386 (bug 1798007)
  ubuntu_ltp_syscalls - inotify07 (bug 1774387) inotify08 (bug 1775784) fanotify07/fanotify08 timeouted (bug 1775165) fanotify09 timeouted (bug 1775153) fanotify10 (bug 1802454) fanotify11 timeouted (bug 1808107)
  xfstests - xfs generic/308 timed out (bug 1738152)

Issue to note in ppc64le (P8):
  ubuntu_kvm_smoke_test - unable to create KVM with uvtool, bug 1755118
  ubuntu_kvm_unit_tests - sprs timed out (bug 1740017)
  ubuntu_ltp_syscalls - inotify07 (bug 1774387) inotify08 (bug 1775784) fanotify07/fanotify08 timeouted (bug 1775165) fanotify09 timeouted (bug 1775153) fanotify10 (bug 1802454) fanotify11 timeouted (bug 1808107)
  xfstests - btrfs generic/176 timed out

Issue to note in s390x (KVM):
  libhugetlbfs - failed 11 killed by signal 7 bad config 1
  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 - 12 failed
  ubuntu_ltp_syscalls - inotify07 (bug 1774387) inotify08 (bug 1775784) fanotify07/fanotify08 timeouted (bug 1775165) fanotify09 timeouted (bug 1775153) fanotify10 (bug 1802454) fanotify11 timeouted (bug 1808107)

Issue to note in s390x (Ubuntu on LPAR):
  libhugetlbfs - failed 11 killed by signal 7 bad config 1
  ubuntu_bpf_jit - unable to insert test_bpf on Xenial s390x (bug 1768452)
  ubuntu_kvm_smoke_test - uvtool issue (bug 1729854)
  ubuntu_ltp_syscalls - inotify07 (bug 1774387) inotify08 (bug 1775784) fanotify07/fanotify08 timeouted (bug 1775165) fanotify09 timeouted (bug 1775153) fanotify10 (bug 1802454) fanotify11 timeouted (bug 1808107)
  ubuntu_lxc - lxc-test-ubuntu failed (Failed to start networking in ubuntu-cloud container)

Issue to note in s390x (zVM):
  libhugetlbfs - failed 11 killed by signal 7 bad config 1
  ubuntu_bpf_jit - u...

[Taihsiang Ho (tai271828)]

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

[Launchpad Janitor (janitor)]

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

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

  * linux: 4.4.0-141.167 -proposed tracker (LP: #1806569)

  * Redpine: firmware assert upon assoc timeout (LP: #1804360)
    - SAUCE: Redpine: fix for firmware assert upon assoc timeout

  * CVE-2018-12896
    - posix-timers: Sanitize overrun handling

  * CVE-2017-5753
    - ALSA: opl3: Hardening for potential Spectre v1
    - ALSA: asihpi: Hardening for potential Spectre v1
    - ALSA: hdspm: Hardening for potential Spectre v1
    - ALSA: rme9652: Hardening for potential Spectre v1
    - ALSA: control: Hardening for potential Spectre v1
    - usbip: vhci_sysfs: fix potential Spectre v1
    - libahci: Fix possible Spectre-v1 pmp indexing in ahci_led_store()

  * CVE-2018-18710
    - cdrom: fix improper type cast, which can leat to information leak.

  * CVE-2018-18690
    - xfs: don't fail when converting shortform attr to long form during
      ATTR_REPLACE

  * CVE-2017-18174
    - pinctrl: Add devm_ apis for pinctrl_{register, unregister}
    - pinctrl: amd: Use devm_pinctrl_register() for pinctrl registration

 -- Khalid Elmously <email address hidden> Wed, 05 Dec 2018 06:11:33 +0000

[Brad Figg (brad-figg)]

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