xenial/linux-raspi2: 4.4.0-1120.129 -proposed tracker

Hardware Certification have begun testing this -proposed kernel.

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

This bug was fixed in the package linux-raspi2 - 4.4.0-1120.129

---------------
linux-raspi2 (4.4.0-1120.129) xenial; urgency=medium

  * xenial/linux-raspi2: 4.4.0-1120.129 -proposed tracker (LP: #1841536)

  [ 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-raspi2 (4.4.0-1119.128) xenial; urgency=medium

  * xenial/linux-raspi2: 4.4.0-1119.128 -proposed tracker (LP: #1840014)

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

  [ 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 in memory shrink
    - bcache: Fix indentation
    - bcache: Add __printf annotation to __bch_check_keys()
    - bcache: Annotate switch fall-through
    - bcache: Fix kernel-doc warnings
    - bcache: Remove an unused variable
    - bcache: Suppress more warnings about set-but-not-used variables
    - bcache: Reduce the number of sparse complaints about lock imbalances
    - bcache: Move couple of functions to sysfs.c
  * CVE-2019-3900
    - vhost: introduce vhost_vq_avail_empty()
    - vhost_net: tx batching
    - vhost_net: do not stall on zerocopy depletion
    - vhost-net: set packet weight of tx polling to 2 * vq size
    - vhost_net: use packet weight for rx handler, too
    - vhost_net: introduce vhost_exceeds_weight()
    - vhost: introduce vhost_exceeds_weight()
    - vhost_net: fix possible infinite loop
    - vhost: scsi: add weight support
  * Xenial: ZFS deadlock in shrinker path with xattrs (LP: #1839521)...

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