bionic/linux-aws-5.4: 5.4.0-1025.25~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: 1894638
packages:
  lrm: linux-restricted-modules-aws-5.4
  main: linux-aws-5.4
  meta: linux-meta-aws-5.4
phase: Complete
phase-changed: Tuesday, 22. September 2020 15:47 UTC
proposed-announcement-sent: true
proposed-testing-requested: true
reason: {}
variant: debs
versions:
  lrm: 5.4.0-1025.25~18.04.1
  main: 5.4.0-1025.25~18.04.1
  meta: 5.4.0.1025.10

[Andy Whitcroft (apw)]

Major kernel version bump requires kernel-signoff when required upgrade testing is complete.

[Stefan Bader (smb)]

Launched an AWS t3.medium, it came up with a 5.3 kernel. Then added ppa:canonical-kernel-team/proposed and ran dist-upgrade, rebooted. Instance came up with 5.4.0-1025-aws #25~18.04.1-Ubuntu.

[Po-Hsu Lin (cypressyew)]

Marked as Incomplete for the seccomp_bpf build issue in kselftests (bug 1896420)

5.4.0-1025.25~18.04.1 - aws
Regression test CMPL, RTB.

Issue to note in x86_64 (aws):
  ubuntu_kernel_selftests - memory-hotplug on some instances kci_test_encap_fou() from rtnetlink.sh in net (bug 1891421) ip6gretap / erspan / ip6erspan in rtnetlink.sh from net (bug 1896448) test_blackhole_dev in net (bug 1851619) pmtu.sh marked as failed (bug 1887661) psock_snd.sh in net (bug 1892213) seccomp_bpf in seccomp failed to build (bug 1896420) nsleep-lat in timers on some instances (bug 1884884)
  ubuntu_kvm_unit_tests - vmx on i3.metal (1821394) vmx_apicv_test on i3.metal (bug 1827866)
  ubuntu_ltp - proc01 (bug 1829849) ksm03 ksm03_1 ksm04 ksm04_1 in mm (bug 1884742) mtest06 on t2.small (bug 1854722) cpuacct_100_100 (bug 1829978) cpuset_hotplug (bug 1834006) cpuset_sched_domains (bug 1830361) memcg_max_usage_in_bytes (bug 1829979) memcg_move_charge_at_immigrate (bug 1837037) memcg_stat (bug 1829983) memcg_subgroup_charge (bug 1847982) memcg_usage_in_bytes (bug 1829984) memcg_use_hierarchy (bug 1829989) cgroup_fj_* failure caused by memcg_test_3 (bug 1836694) on t2.small getaddrinfo_01 (bug 1829995) crypto_user02 (bug 1837543) tpci (bug 1878389)
  ubuntu_ltp_syscalls - btrfs fill_fs test in fallocate06 (bug 1866323) kill11 (bug 1865965) msgstress03 on some nodes (bug 1783881)
  ubuntu_lxc - lxc-test-device-add-remove from ubuntu_lxc (bug 1884024)
  ubuntu_sysdig_smoke_test - test failed with 0 read / write event from dd (bug 1844493)

Skipped / blacklisted:
 * libhugetlbfs

Issue to note in arm64 (aws):
  ubuntu_bpf - valid read map access into a read-only array failed on ARM64 in test_verifier (bug 1845870)
  ubuntu_kernel_selftests - memory-hotplug not executable on arm64 (bug 1892816) kci_test_encap_fou() from rtnetlink.sh in net (bug 1891421) ip6gretap / erspan / ip6erspan in rtnetlink.sh from net (bug 1896448) test_blackhole_dev in net (bug 1851619) pmtu.sh marked as failed (bug 1887661) psock_snd.sh in net (bug 1892213)
  ubuntu_ltp - proc01 (bug 1829849) ksm03 ksm03_1 ksm04 ksm04_1 in mm (bug 1884742) cpuacct_100_100 (bug 1829978) memcg_max_usage_in_bytes (bug 1829979) memcg_move_charge_at_immigrate (bug 1837037) memcg_stat (bug 1829983) memcg_stat_rss (bug 1837035) memcg_usage_in_bytes (bug 1829984) memcg_use_hierarchy (bug 1829989) cgroup_fj_* failure caused by memcg_test_3 (bug 1836694) getaddrinfo_01 (bug 1829995) tpci (bug 1878389)
  ubuntu_ltp_syscalls - btrfs fill_fs test in fallocate06 (bug 1866323) kill11 (bug 1865965) msgstress03 on some nodes (bug 1783881)
  ubuntu_lxc - lxc-test-device-add-remove from ubuntu_lxc (bug 1884024)

Skipped / blacklisted:
 * iosched_bugs
 * libhugetlbfs
 * tsc
 * ubuntu_32_on_64
 * ubuntu_seccomp
 * ubuntu_sysdig_smoke_test

[Sean Feole (sfeole)]

We are not holding the kernel up due to bug: 1896420

Marking resolved and moving along.

[Launchpad Janitor (janitor)]

This bug was fixed in the package linux-aws-5.4 - 5.4.0-1025.25~18.04.1

---------------
linux-aws-5.4 (5.4.0-1025.25~18.04.1) bionic; urgency=medium

  * bionic/linux-aws-5.4: 5.4.0-1025.25~18.04.1 -proposed tracker (LP: #1894637)

  * Packaging resync (LP: #1786013)
    - [Packaging] update variants

  [ Ubuntu: 5.4.0-1025.25 ]

  * focal/linux-aws: 5.4.0-1025.25 -proposed tracker (LP: #1894638)
  * focal/linux: 5.4.0-48.52 -proposed tracker (LP: #1894654)
  * mm/slub kernel oops on focal kernel 5.4.0-45 (LP: #1895109)
    - SAUCE: Revert "mm/slub: fix a memory leak in sysfs_slab_add()"
  * Packaging resync (LP: #1786013)
    - update dkms package versions
    - update dkms package versions
  * Introduce the new NVIDIA 450-server and the 450 UDA series (LP: #1887674)
    - [packaging] add signed modules for nvidia 450 and 450-server
  * [UBUNTU 20.04] zPCI attach/detach issues with PF/VF linking support
    (LP: #1892849)
    - s390/pci: fix zpci_bus_link_virtfn()
    - s390/pci: re-introduce zpci_remove_device()
    - s390/pci: fix PF/VF linking on hot plug
  * [UBUNTU 20.04] kernel: s390/cpum_cf,perf: changeDFLT_CCERROR counter name
    (LP: #1891454)
    - s390/cpum_cf, perf: change DFLT_CCERROR counter name
  * [UBUNTU 20.04] zPCI: Enabling of a reserved PCI function regression
    introduced by multi-function support (LP: #1891437)
    - s390/pci: fix enabling a reserved PCI function
  * CVE-2020-12888
    - vfio/type1: Support faulting PFNMAP vmas
    - vfio-pci: Fault mmaps to enable vma tracking
    - vfio-pci: Invalidate mmaps and block MMIO access on disabled memory
  * [Hyper-V] VSS and File Copy daemons intermittently fails to start
    (LP: #1891224)
    - [Packaging] Bind hv_vss_daemon startup to hv_vss device
    - [Packaging] bind hv_fcopy_daemon startup to hv_fcopy device
  * alsa/hdmi: support nvidia mst hdmi/dp audio (LP: #1867704)
    - ALSA: hda - Rename snd_hda_pin_sense to snd_hda_jack_pin_sense
    - ALSA: hda - Add DP-MST jack support
    - ALSA: hda - Add DP-MST support for non-acomp codecs
    - ALSA: hda - Add DP-MST support for NVIDIA codecs
    - ALSA: hda: hdmi - fix regression in connect list handling
    - ALSA: hda: hdmi - fix kernel oops caused by invalid PCM idx
    - ALSA: hda: hdmi - preserve non-MST PCM routing for Intel platforms
    - ALSA: hda: hdmi - Keep old slot assignment behavior for Intel platforms
    - ALSA: hda - Fix DP-MST support for NVIDIA codecs
  * Focal update: v5.4.60 upstream stable release (LP: #1892899)
    - smb3: warn on confusing error scenario with sec=krb5
    - genirq/affinity: Make affinity setting if activated opt-in
    - genirq/PM: Always unlock IRQ descriptor in rearm_wake_irq()
    - PCI: hotplug: ACPI: Fix context refcounting in acpiphp_grab_context()
    - PCI: Add device even if driver attach failed
    - PCI: qcom: Define some PARF params needed for ipq8064 SoC
    - PCI: qcom: Add support for tx term offset for rev 2.1.0
    - btrfs: allow use of global block reserve for balance item deletion
    - btrfs: free anon block device right after subvolume deletion
    - btrfs: don't allocate anonymous block device for user invisible roots
    - btrfs: ref-verify: fix m...

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

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