bionic/linux: 4.15.0-56.62 -proposed tracker

[Kleber Sacilotto de Souza]

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

derivatives: bug 1837586 (linux-raspi2), bug 1837590 (linux-snapdragon), bug 1837614 (linux-ibm-gt), bug 1837616 (linux-oracle), bug 1837617 (linux-fips)

-- swm properties --
boot-testing-requested: true
bugs-spammed: true
packages:
  lrm: linux-restricted-modules
  main: linux
  meta: linux-meta
  signed: linux-signed
phase: Testing
phase-changed: Friday, 26. July 2019 09:38 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
trackers:
  bionic/linux-aws: bug 1837599
  bionic/linux-fips: bug 1837617
  bionic/linux-gcp: bug 1837608
  bionic/linux-gke-4.15: bug 1837612
  bionic/linux-ibm-gt: bug 1837614
  bionic/linux-kvm: bug 1837613
  bionic/linux-oem: bug 1837593
  bionic/linux-oracle: bug 1837616
  bionic/linux-raspi2: bug 1837586
  bionic/linux-snapdragon: bug 1837590
  bionic/linux/pc-kernel: bug 1837582
  bionic/linux/pc-lowlatency-kernel: bug 1837583
  xenial/linux-azure: bug 1837622
  xenial/linux-hwe: bug 1837625
variant: debs

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

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

linux-restricted-modules 4.15.0-56.62 - is in universe instead of restricted
linux-modules-nvidia-390-4.15.0-56-generic 4.15.0-56.62 - is in universe instead of restricted
linux-modules-nvidia-390-4.15.0-56-lowlatency 4.15.0-56.62 - is in universe instead of restricted
linux-modules-nvidia-390-generic 4.15.0-56.62 - is in universe instead of restricted
linux-modules-nvidia-390-lowlatency 4.15.0-56.62 - is in universe instead of restricted

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

[Dmitry S. Fedorov (fedusia)]

Problem exists in kernel 4.15.0-56.62. Servers worked fine about 1 day and then unresponsible. I cant to log in via ssh, just only can print screen via ipmi.

[Launchpad Janitor (janitor)]

This bug was fixed in the package linux - 4.15.0-58.64

---------------
linux (4.15.0-58.64) bionic; urgency=medium

  * unable to handle kernel NULL pointer dereference at 000000000000002c (IP:
    iget5_locked+0x9e/0x1f0) (LP: #1838982)
    - Revert "ovl: set I_CREATING on inode being created"
    - Revert "new primitive: discard_new_inode()"

linux (4.15.0-57.63) bionic; urgency=medium

  * CVE-2019-1125
    - x86/cpufeatures: Carve out CQM features retrieval
    - x86/cpufeatures: Combine word 11 and 12 into a new scattered features word
    - x86/speculation: Prepare entry code for Spectre v1 swapgs mitigations
    - x86/speculation: Enable Spectre v1 swapgs mitigations
    - x86/entry/64: Use JMP instead of JMPQ
    - x86/speculation/swapgs: Exclude ATOMs from speculation through SWAPGS

  * Packaging resync (LP: #1786013)
    - update dkms package versions

linux (4.15.0-56.62) bionic; urgency=medium

  * bionic/linux: 4.15.0-56.62 -proposed tracker (LP: #1837626)

  * Packaging resync (LP: #1786013)
    - [Packaging] resync git-ubuntu-log
    - [Packaging] update helper scripts

  * CVE-2019-2101
    - media: uvcvideo: Fix 'type' check leading to overflow

  * hibmc-drm Causes Unreadable Display for Huawei amd64 Servers (LP: #1762940)
    - [Config] Set CONFIG_DRM_HISI_HIBMC to arm64 only
    - SAUCE: Make CONFIG_DRM_HISI_HIBMC depend on ARM64

  * Bionic: support for Solarflare X2542 network adapter (sfc driver)
    (LP: #1836635)
    - sfc: make mem_bar a function rather than a constant
    - sfc: support VI strides other than 8k
    - sfc: add Medford2 (SFC9250) PCI Device IDs
    - sfc: improve PTP error reporting
    - sfc: update EF10 register definitions
    - sfc: populate the timer reload field
    - sfc: update MCDI protocol headers
    - sfc: support variable number of MAC stats
    - sfc: expose FEC stats on Medford2
    - sfc: expose CTPIO stats on NICs that support them
    - sfc: basic MCDI mapping of 25/50/100G link speeds
    - sfc: support the ethtool ksettings API properly so that 25/50/100G works
    - sfc: add bits for 25/50/100G supported/advertised speeds
    - sfc: remove tx and MCDI handling from NAPI budget consideration
    - sfc: handle TX timestamps in the normal data path
    - sfc: add function to determine which TX timestamping method to use
    - sfc: use main datapath for HW timestamps if available
    - sfc: only enable TX timestamping if the adapter is licensed for it
    - sfc: MAC TX timestamp handling on the 8000 series
    - sfc: on 8000 series use TX queues for TX timestamps
    - sfc: only advertise TX timestamping if we have the license for it
    - sfc: simplify RX datapath timestamping
    - sfc: support separate PTP and general timestamping
    - sfc: support second + quarter ns time format for receive datapath
    - sfc: support Medford2 frequency adjustment format
    - sfc: add suffix to large constant in ptp
    - sfc: mark some unexported symbols as static
    - sfc: update MCDI protocol headers
    - sfc: support FEC configuration through ethtool
    - sfc: remove ctpio_dmabuf_start from stats
    - sfc: stop the TX queue before pushing new buffers

  * [18.04 FEAT] zKVM: Add hardwar...