eoan/linux-azure: 5.3.0-1028.29 -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: 1880111
packages:
  lrm: linux-restricted-modules-azure
  main: linux-azure
  meta: linux-meta-azure
  signed: linux-signed-azure
phase: Complete
phase-changed: Wednesday, 10. June 2020 00:45 UTC
proposed-announcement-sent: true
proposed-testing-requested: true
reason: {}
trackers:
  bionic/linux-azure-5.3: bug 1878808
variant: debs
versions:
  lrm: 5.3.0-1028.29
  main: 5.3.0-1028.29
  meta: 5.3.0.1028.47
  signed: 5.3.0-1028.29

[Launchpad Janitor (janitor)]

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

---------------
linux-azure (5.3.0-1028.29) eoan; urgency=medium

  [ Ubuntu: 5.3.0-59.53 ]

  * 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.0-1023.24) eoan; urgency=medium

  * 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

  [ Ubuntu: 5.3.0-56.50 ]

  * 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
  * Eoan update: upstream stable patchset 2020-05-11 (LP: #1878073)
    - ext4: fix extent_status fragmentation for plain files
    -...

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

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