xenial/linux-aws: 4.4.0-1091.102 -proposed tracker

[Stefan Bader]

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-aws
  meta: linux-meta-aws
phase: Signoff
phase-changed: Monday, 26. August 2019 15:46 UTC
proposed-announcement-sent: true
proposed-testing-requested: true
reason:
  security-signoff: Stalled -- waiting for signoff
  verification-testing: Ongoing -- testing in progress
trackers:
  xenial/linux-aws/aws-kernel: bug 1840009
variant: debs

[Po-Hsu Lin (cypressyew)]

4.4.0-1091.102 - aws
Regression test CMPL, RTB.

Issue to note in x86_64 (aws):
  ubuntu_kernel_selftests - cpu_hotplug (bug 1812149) on t2.small
  ubuntu_kvm_unit_tests - apic timeouted (bug 1748103) vmx (bug 1821394) vmx_hlt_with_rvi_test (bug 1822308) vmx_apic_passthrough_thread (bug 1822309) debug (bug 1821906) failed on i3.metal
  ubuntu_ltp - should be skipped
  ubuntu_ltp_syscalls - fanotify06 (bug 1833028) fanotify07 blacklisted (bug 1775165) fanotify09 (bug 1775153) fanotify10 (bug 1802454) inotify07 (bug 1774387) inotify08 (bug 1775784) leapsec01 (bug 1839135) sync_file_range02 (bug 1819116)
  ubuntu_zram_smoke_test - failed on i3.metal only, passed on the rest

Skipped / blacklisted:
 * ubuntu_ltp
 * ubuntu_seccomp
 * ubuntu_sysdig_smoke_test

[Launchpad Janitor (janitor)]

This bug was fixed in the package linux-aws - 4.4.0-1092.103

---------------
linux-aws (4.4.0-1092.103) xenial; urgency=medium

  * xenial/linux-aws: 4.4.0-1092.103 -proposed tracker (LP: #1841533)

  [ Ubuntu: 4.4.0-161.189 ]

  * xenial/linux: 4.4.0-161.189 -proposed tracker (LP: #1841544)
  * flock not mediated by 'k' (LP: 1658219)
    - Revert "UBUNTU: SAUCE: apparmor: flock mediation is not being, enforced on
      cache check"
  * Packaging resync (LP: #1786013)
    - [Packaging] resync getabis

linux-aws (4.4.0-1091.102) xenial; urgency=medium

  * xenial/linux-aws: 4.4.0-1091.102 -proposed tracker (LP: #1840010)

  * CVE-2019-10638
    - [Config] aws: CONFIG_TEST_HASH=n

  * Add the EFA driver into linux-aws (LP: #1837638)
    - RDMA/efa: Add EFA device definitions
    - RDMA/efa: Add the ABI definitions
    - RDMA/efa: Add the efa.h header file
    - RDMA/efa: Add the efa_com.h file
    - RDMA/efa: Add the com service API definitions
    - RDMA/efa: Implement functions that submit and complete admin commands
    - RDMA/efa: Add common command handlers
    - RDMA/efa: Add EFA verbs implementation
    - RDMA/efa: Add the efa module
    - RDMA/efa: Add driver to Kconfig/Makefile
    - [Config] aws: CONFIG_INFINIBAND_EFA=m
    - RDMA/efa: Remove MAYEXEC flag check from mmap flow
    - RDMA/efa: Fix success return value in case of error
    - RDMA/efa: Handle mmap insertions overflow
    - SAUCE: Add kernel compatibility fixups
    - SAUCE: linux/efa: Be consistent with success flow return value
    - SAUCE: linux/efa: Entropy in admin commands id
    - SAUCE: linux/efa: Fix modify QP udata check backport

  [ Ubuntu: 4.4.0-160.188 ]

  * xenial/linux: 4.4.0-160.188 -proposed tracker (LP: #1840021)
  * Packaging resync (LP: #1786013)
    - [Packaging] update helper scripts
  * EeePC 1005px laptop backlight is off after system boot up (LP: #1837117)
    - platform/x86: asus-wmi: Only Tell EC the OS will handle display hotkeys from
      asus_nb_wmi
  * CVE-2019-10638
    - [Config] CONFIG_TEST_HASH=n
    - siphash: add cryptographically secure PRF
    - inet: switch IP ID generator to siphash
  * Stacked onexec transitions fail when under NO NEW PRIVS restrictions
    (LP: #1839037)
    - SAUCE: apparmor: fix nnp subset check failure, when stacking
  * AppArmor onexec transition causes WARN kernel stack trace (LP: #1838627)
    - SAUCE: apparmor: fix audit failures when performing profile transitions
  * flock not mediated by 'k' (LP: 1658219) // Ubuntu 16.04: read access
    incorrectly implies 'm' rule (LP: 1838090)
    - SAUCE: apparmor: flock mediation is not being, enforced on cache check
  * bcache: bch_allocator_thread(): hung task timeout (LP: #1784665) // Tight
    timeout for bcache removal causes spurious failures (LP: #1796292)
    - SAUCE: bcache: fix deadlock in bcache_allocator
  * bcache: bch_allocator_thread(): hung task timeout (LP: #1784665)
    - bcache: improve bcache_reboot()
    - bcache: add journal statistic
    - bcache: fix high CPU occupancy during journal
    - bcache: fix incorrect sysfs output value of strip size
    - bcache: fix error return value in memory shrink
    - bcache: fix using of loop variable i...