bionic/linux-oem-osp1: 5.0.0-1019.21 -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:
  lrm: linux-restricted-modules-oem-osp1
  main: linux-oem-osp1
  meta: linux-meta-oem-osp1
  signed: linux-signed-oem-osp1
phase: Testing
phase-changed: Tuesday, 20. August 2019 00:20 UTC
proposed-announcement-sent: true
proposed-testing-requested: true
reason:
  automated-testing: Stalled -- testing FAILED
  certification-testing: Ongoing -- testing in progress
  regression-testing: Ongoing -- testing in progress
  security-signoff: Pending -- waiting for signoff
  verification-testing: Ongoing -- testing in progress
variant: debs

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

The following packages ended up in the wrong component in the -proposed pocket:

linux-restricted-modules-oem-osp1 5.0.0-1019.21 - is in universe instead of multiverse
linux-modules-nvidia-390-5.0.0-1019-oem-osp1 5.0.0-1019.21 - is in universe instead of multiverse
linux-modules-nvidia-390-oem-osp1 5.0.0-1019.21 - is in universe instead of multiverse
linux-modules-nvidia-418-5.0.0-1019-oem-osp1 5.0.0-1019.21 - is in universe instead of multiverse
linux-modules-nvidia-418-oem-osp1 5.0.0-1019.21 - is in universe instead of multiverse

Once this is fixed, set the promote-to-proposed to Fix Released again

[Launchpad Janitor (janitor)]

This bug was fixed in the package linux-oem-osp1 - 5.0.0-1020.22

---------------
linux-oem-osp1 (5.0.0-1020.22) bionic; urgency=medium

  * bionic/linux-oem-osp1: 5.0.0-1020.22 -proposed tracker (LP: #1840815)

  [ Ubuntu: 5.0.0-27.28 ]

  * disco/linux: 5.0.0-27.28 -proposed tracker (LP: #1840816)
  * [Potential Regression] System crashes when running ftrace test in
    ubuntu_kernel_selftests (LP: #1840750)
    - x86/kprobes: Set instruction page as executable

 -- Timo Aaltonen <email address hidden> Thu, 22 Aug 2019 13:55:10 +0300

[Launchpad Janitor (janitor)]

This bug was fixed in the package linux-oem-osp1 - 5.0.0-1022.24

---------------
linux-oem-osp1 (5.0.0-1022.24) bionic; urgency=medium

  [ Ubuntu: 5.0.0-29.31 ]

  * powerpc/tm: Fix restoring FP/VMX facility incorrectly on interrupts
    (CVE-2019-15031) / powerpc/tm: Fix FP/VMX unavailable exceptions inside a
    transaction (CVE-2019-15030) (LP: #1843533) // CVE-2019-15031
    - powerpc/tm: Fix FP/VMX unavailable exceptions inside a transaction
    - powerpc/tm: Fix restoring FP/VMX facility incorrectly on interrupts
  * CVE-2019-14835
    - vhost: fix dirty log buffer overflow
  * Packaging resync (LP: #1786013)
    - [Packaging] resync getabis

 -- Stefan Bader <email address hidden> Thu, 12 Sep 2019 20:27:12 +0200