bionic/linux-azure-5.3: 5.3.0-1028.29~18.04.1 -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

-- swm properties --
boot-testing-requested: true
kernel-stable-master-bug: 1878809
packages:
  lrm: linux-restricted-modules-azure-5.3
  main: linux-azure-5.3
  meta: linux-meta-azure-5.3
  signed: linux-signed-azure-5.3
phase: Complete
phase-changed: Wednesday, 10. June 2020 01:17 UTC
proposed-announcement-sent: true
proposed-testing-requested: true
reason: {}
trackers:
  bionic/linux-azure-5.3/azure-kernel: bug 1878807
variant: debs
versions:
  lrm: 5.3.0-1028.29~18.04.1
  main: 5.3.0-1028.29~18.04.1
  meta: 5.3.0.1028.25
  signed: 5.3.0-1028.29~18.04.1

[Po-Hsu Lin (cypressyew)]

5.3.0-1023.24~18.04.1 - azure
Regression test CMPL, RTB.

Issue to note in x86_64 (azure):
  ubuntu_bpf - test_maps in ubuntu_bpf failed with Failed to load SK_SKB verdict prog (bug 1845860)
  ubuntu_kernel_selftests - test_bpf in net (bug 1812189) test_blackhole_dev in net (bug 1851619) msg_zerocopy in net (bug 1812620) xfrm_policy.sh / pmtu.sh / udpgso_bench.sh timeout in net (bug 1856010) msg_zerocopy in net (bug 1812620)
  ubuntu_kvm_unit_tests - not tested on bare-metals this cycle
  ubuntu_ltp - proc01 (bug 1829849) cpuset_hotplug (bug 1834006) memcg_max_usage_in_bytes (bug 1829979) memcg_stat (bug 1829983) memcg_usage_in_bytes (bug 1829984) memcg_use_hierarchy (bug 1829989) cpuhotplug02 (bug 1836166) cpuhotplug03 (bug 1836167) cpuhotplug04 (bug 1836169) cpuhotplug06 (bug 1836170) getaddrinfo_01 (bug 1829995) crypto_user02 (bug 1837543)
  ubuntu_ltp_syscalls - btrfs fill_fs test in fallocate06 (bug 1866323) fanotify09 case 3 (bug 1876684) fanotify15 (bug 1878748) kill11 (bug 1865965) msgstress03 (bug 1797341)
  ubuntu_lxc - lxc-test-no-new-privs (failed to fetch package) on Standard_B1ms, Standard_DS5_v2 (bug 1821152), passed on the rest
  ubuntu_sysdig_smoke_test - test failed with 0 read / write event from dd (bug 1844493)

Skipped / blacklisted:
  * libhugetlbfs

[Launchpad Janitor (janitor)]

This bug was fixed in the package linux-azure-5.3 - 5.3.0-1028.29~18.04.1

---------------
linux-azure-5.3 (5.3.0-1028.29~18.04.1) bionic; urgency=medium

  [ Ubuntu: 5.3.0-1028.29 ]

  * CVE-2020-0543
    - SAUCE: x86/speculation/spectre_v2: Exclude Zhaoxin CPUs from SPECTRE_V2
    - SAUCE: x86/cpu: Add a steppings field to struct x86_cpu_id
    - SAUCE: x86/cpu: Add 'table' argument to cpu_matches()
    - SAUCE: x86/speculation: Add Special Register Buffer Data Sampling (SRBDS)
      mitigation
    - SAUCE: x86/speculation: Add SRBDS vulnerability and mitigation documentation
    - SAUCE: x86/speculation: Add Ivy Bridge to affected list

linux-azure-5.3 (5.3.0-1023.24~18.04.1) bionic; urgency=medium

  * bionic/linux-azure-5.3: 5.3.0-1023.24~18.04.1 -proposed tracker
    (LP: #1878808)

  [ Ubuntu: 5.3.0-1023.24 ]

  * eoan/linux-azure: 5.3.0-1023.24 -proposed tracker (LP: #1878809)
  * Build and ship a signed wireguard.ko (LP: #1861284)
    - [Config] azure: wireguard -- enable on all architectures
  * linux-azure: Enable FSGSBASE instructions to support SGX (LP: #1877425)
    - SAUCE: x86/ptrace: Prevent ptrace from clearing the FS/GS selector
    - SAUCE: selftests/x86/fsgsbase: Test GS selector on ptracer-induced GS base
      write
    - SAUCE: x86/cpu: Add 'unsafe_fsgsbase' to enable CR4.FSGSBASE
    - SAUCE: x86/entry/64: Clean up paranoid exit
    - SAUCE: x86/entry/64: Switch CR3 before SWAPGS in paranoid entry
    - SAUCE: x86/entry/64: Introduce the FIND_PERCPU_BASE macro
    - SAUCE: x86/entry/64: Handle FSGSBASE enabled paranoid entry/exit
    - SAUCE: x86/entry/64: Document GSBASE handling in the paranoid path
    - SAUCE: x86/fsgsbase/64: Add intrinsics for FSGSBASE instructions
    - SAUCE: x86/fsgsbase/64: Enable FSGSBASE instructions in helper functions
    - SAUCE: x86/fsgsbase/64: Use FSGSBASE in switch_to() if available
    - SAUCE: x86/fsgsbase/64: Use FSGSBASE instructions on thread copy and ptrace
    - SAUCE: x86/speculation/swapgs: Check FSGSBASE in enabling SWAPGS mitigation
    - SAUCE: selftests/x86/fsgsbase: Test ptracer-induced GS base write with
      FSGSBASE
    - SAUCE: x86/fsgsbase/64: Enable FSGSBASE on 64bit by default and add a
      chicken bit
    - SAUCE: x86/elf: Enumerate kernel FSGSBASE capability in AT_HWCAP2
    - SAUCE: Documentation/x86/64: Add documentation for GS/FS addressing mode
  * eoan/linux: 5.3.0-56.50 -proposed tracker (LP: #1880111)
  * Build and ship a signed wireguard.ko (LP: #1861284)
    - [Packaging] wireguard -- add support for building signed .ko
    - [Config] wireguard -- enable on all architectures
  * Packaging resync (LP: #1786013)
    - update dkms package versions
  * debian/scripts/file-downloader does not handle positive failures correctly
    (LP: #1878897)
    - [Packaging] file-downloader not handling positive failures correctly
  * Killer(R) Wi-Fi 6 AX1650i 160MHz Wireless Network Adapter (201NGW),
    REV=0x354 [8086:a0f0] subsystem id [1a56:1651] wireless adapter not found
    due to firmware crash (LP: #1874685)
    - iwlwifi: pcie: handle QuZ configs with killer NICs as well
  * CVE-2020-12114
    - propagate_one(): mnt_set_mountpoint() needs mount_lock
  * ...

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

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