linux-azure: 4.15.0-1034.35~16.04.1 -proposed tracker

[Marcelo Cerri]

This bug is for tracking the 4.15.0-1034.35~16.04.1 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
-- swm properties --
boot-testing-requested: true
kernel-stable-master-bug: 1803592
phase: Promoted to proposed
phase-changed: Wednesday, 28. November 2018 15:41 UTC
proposed-announcement-sent: true
proposed-testing-requested: true
reason:
  automated-testing: Testing FAILED
  snap-release-to-candidate: Snap not in candidate channel
  stakeholder-signoff: Waiting for signoff

[Joshua R. Poulson (jrp)]

Watching for build.

[Po-Hsu Lin (cypressyew)]

4.15.0-1034.35~16.04.1 - azure
Regression test CMPL, RTB.

Issue to note in x86_64 (azure):
  libhugetlbfs - 1 failed (brk_near_huge, bug 1653597), Killed by signal 1, bad config 3, failed on Standard_B1ms and Standard_F1s only
  monotonic_time - all two tests (or just tsc test) failed on some instances, passed on the rest
  ubuntu_kvm_unit_tests - test skipped due to no KVM support, vmx_control will crash E4 nodes (bug 1747892)
  ubuntu_ltp_syscalls - fanotify09-2 (bug 1804594) fanotify10 (bug 1802454) inotify08 (bug 1775784) quotactl01 failed (bug 1790028) statx05 (bug 1798524)
  ubuntu_lxc - lxc-test-ubuntu (Too many open files) failed on Standard_D2s_v3 only
  ubunut_qrt_apparmor - mmap test timed out on some nodes (bug 1783922)
  ubuntu_vfat_stress - failed on Standard_A2_v2 only

Skipped / blacklisted:
  * ubuntu_ltp
  * ubuntu_seccomp

[Launchpad Janitor (janitor)]

This bug was fixed in the package linux-azure - 4.15.0-1035.36~16.04.1

---------------
linux-azure (4.15.0-1035.36~16.04.1) xenial; urgency=medium

  * linux-azure: 4.15.0-1035.36~16.04.1 -proposed tracker (LP: #1806034)

  [ Ubuntu: 4.15.0-1035.36 ]

  * linux-azure: 4.15.0-1035.36 -proposed tracker (LP: #1806021)
  * [Hyper-V] Additional patches for Lv2 storage performance (LP: #1805304)
    - SAUCE: scsi: storvsc: Fix a race in sub-channel creation that can cause
      panic

linux-azure (4.15.0-1034.35~16.04.1) xenial; urgency=medium

  * linux-azure: 4.15.0-1034.35~16.04.1 -proposed tracker (LP: #1805434)

  [ Ubuntu: 4.15.0-1034.35 ]

  * linux-azure: 4.15.0-1034.35 -proposed tracker (LP: #1805412)
  * [Hyper-V] Additional patches for Lv2 storage performance (LP: #1805304)
    - SAUCE: Drivers: hv: vmbus: Remove x86-isms from arch independent drivers
    - SAUCE: x86/hyperv: Add a function to read both TSC and TSC page value
      simulateneously
    - SAUCE: x86/hyperv: Reenlightenment notifications support
    - SAUCE: x86/hyperv: Redirect reenlightment notifications on CPU offlining
    - SAUCE: x86/hyper-v: move hyperv.h out of uapi
    - SAUCE: x86/hyper-v: move definitions from TLFS to hyperv-tlfs.h
    - SAUCE: x86/hyper-v: allocate and use Virtual Processor Assist Pages
    - SAUCE: x86/hyper-v: define struct hv_enlightened_vmcs and clean field bits
    - SAUCE: X86/Hyper-V: Enlighten APIC access
    - SAUCE: X86/Hyper-V: Enable IPI enlightenments
    - SAUCE: X86/Hyper-V: Enhanced IPI enlightenment
    - SAUCE: x86/hyper-v: Fix the circular dependency in IPI enlightenment

linux-azure (4.15.0-1033.34~16.04.1) xenial; urgency=medium

  * linux-azure: 4.15.0-1033.34~16.04.1 -proposed tracker (LP: #1802565)

  [ Ubuntu: 4.15.0-1033.34 ]

  * linux-azure: 4.15.0-1033.34 -proposed tracker (LP: #1802559)
  * linux: 4.15.0-42.45 -proposed tracker (LP: #1803592)
  * [FEAT] Guest-dedicated Crypto Adapters (LP: #1787405)
    - KVM: s390: reset crypto attributes for all vcpus
    - KVM: s390: vsie: simulate VCPU SIE entry/exit
    - KVM: s390: introduce and use KVM_REQ_VSIE_RESTART
    - KVM: s390: refactor crypto initialization
    - s390: vfio-ap: base implementation of VFIO AP device driver
    - s390: vfio-ap: register matrix device with VFIO mdev framework
    - s390: vfio-ap: sysfs interfaces to configure adapters
    - s390: vfio-ap: sysfs interfaces to configure domains
    - s390: vfio-ap: sysfs interfaces to configure control domains
    - s390: vfio-ap: sysfs interface to view matrix mdev matrix
    - KVM: s390: interface to clear CRYCB masks
    - s390: vfio-ap: implement mediated device open callback
    - s390: vfio-ap: implement VFIO_DEVICE_GET_INFO ioctl
    - s390: vfio-ap: zeroize the AP queues
    - s390: vfio-ap: implement VFIO_DEVICE_RESET ioctl
    - KVM: s390: Clear Crypto Control Block when using vSIE
    - KVM: s390: vsie: Do the CRYCB validation first
    - KVM: s390: vsie: Make use of CRYCB FORMAT2 clear
    - KVM: s390: vsie: Allow CRYCB FORMAT-2
    - KVM: s390: vsie: allow CRYCB FORMAT-1
    - KVM: s390: vsie: allow CRYCB FORMAT-0
    - KVM: s390: vsie: allow guest FORMAT-0 CRYCB on host FORMAT-1
    - KVM: ...