bionic/linux-hwe-edge: 5.3.0-21.22~18.04.1 -proposed tracker

Bug #1850485 reported by Khaled El Mously on 2019-10-29
18
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Kernel SRU Workflow
Medium
Unassigned
Automated-testing
Medium
Canonical Kernel Team
Certification-testing
Medium
Canonical Hardware Certification
Prepare-package
Medium
Khaled El Mously
Prepare-package-meta
Medium
Khaled El Mously
Prepare-package-signed
Medium
Khaled El Mously
Promote-to-proposed
Medium
Andy Whitcroft
Promote-to-security
Medium
Ubuntu Stable Release Updates Team
Promote-to-updates
Medium
Ubuntu Stable Release Updates Team
Regression-testing
Medium
Po-Hsu Lin
Security-signoff
Medium
Canonical Security Team
Verification-testing
Medium
Canonical Kernel Team
linux-hwe-edge (Ubuntu)
Undecided
Unassigned
Bionic
Medium
Unassigned

Bug Description

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
packages:
  main: linux-hwe-edge
  meta: linux-meta-hwe-edge
  signed: linux-signed-hwe-edge
phase: Holding before Promote to Updates
phase-changed: Monday, 11. November 2019 10:44 UTC
proposed-announcement-sent: true
proposed-testing-requested: true
variant: debs

tags: added: bionic kernel-release-tracking-bug
Changed in linux-hwe-edge (Ubuntu Bionic):
status: New → Confirmed
Changed in linux-hwe-edge (Ubuntu):
status: New → Invalid
Changed in linux-hwe-edge (Ubuntu Bionic):
importance: Undecided → Medium
tags: added: kernel-release-tracking-bug-live
description: updated
tags: added: kernel-sru-cycle-2019.10.21-3
description: updated
description: updated
tags: added: kernel-sru-backport-of-1850486
Changed in kernel-sru-workflow:
status: New → In Progress
importance: Undecided → Medium
summary: - linux-hwe-edge: <version to be filled> -proposed tracker
+ bionic/linux-hwe-edge: <version to be filled> -proposed tracker
description: updated
summary: - bionic/linux-hwe-edge: <version to be filled> -proposed tracker
+ bionic/linux-hwe-edge: 5.3.0-21.22~18.04.1 -proposed tracker
description: updated
description: updated
description: updated
description: updated
description: updated
tags: added: block-proposed-bionic
tags: added: block-proposed
description: updated
description: updated
description: updated
description: updated
description: updated
description: updated
description: updated
description: updated
description: updated
description: updated
description: updated
Po-Hsu Lin (cypressyew) wrote :
Download full text (9.2 KiB)

5.3.0-21.22~18.04.1 - lowlatency
Regression test CMPL, RTB.

Issue to note in amd64:
  ubuntu_bpf - test_maps failed with BTF is required (bug 1850123)
  ubuntu_kernel_selftests - psock_snd in net (bug 1812618)
  ubuntu_ltp - proc01 (bug 1829849) fs_fill (bug 1842266) vma05 (bug 1845863) memcg_max_usage_in_bytes (bug 1829979) memcg_stat (bug 1829983) memcg_use_hierarchy (bug 1829989) memcg_usage_in_bytes (bug 1829984) cpuset_hotplug (bug 1834006) getaddrinfo_01 (bug 1829995) crypto_user02 (bug 1837543)
  ubuntu_ltp_syscalls - fallocate04, fallocate05, fdatasync03, fremovexattr01, fremovexattr02, fsync01, fsync04, fanotify15, msync04, preadv03, preadv03_64, preadv203, preadv203_64, pwritev03, pwritev03_64, sync03, syncfs01, sync_file_range02, copy_file_range01, statx04 (bug 1842266) fsetxattr01, fgetxattr01, fanotify13, fanotify14, lremovexattr01, setxattr01 (bug 1842266)
  ubuntu_lttng_smoke_test - failed to build lttng module on 5.3 Bionic (bug 1844764)
  ubuntu_qrt_kernel_security - test_140_kernel_modules_not_tainted (bug 1850888)
  ubuntu_sysdig_smoke_test - failed to build sysdig DKMS with 5.3 kernel (bug 1844766)
  ubuntu_xfstests_btrfs - generic/166 time out
  ubuntu_xfstests_ext4 - generic/256 time out
  ubuntu_xfstests_xfs - generic/430 time out

54 / 55 tests were run, missing: ubuntu_xfstests_xfs
Issue to note in i386:
  ubuntu_bpf - test_maps failed with BTF is required (bug 1850123)
  ubuntu_kernel_selftests - psock_snd in net (bug 1812618)
  ubuntu_kvm_unit_tests - vmexit* on i386 (bug 1822235)
  ubuntu_ltp - proc01 (bug 1829849) fs_fill (bug 1842266) memcg_max_usage_in_bytes (bug 1829979) memcg_stat (bug 1829983) memcg_use_hierarchy (bug 1829989) memcg_usage_in_bytes (bug 1829984) getaddrinfo_01 (bug 1829995) cve-2015-3290 (bug 1837005) cve-2017-17053 / cve-2017-1000380 failed because of cve-2015-3290 (bug 1837005) crypto_user02 (bug 1837543) zram02 (bug 1829992)
  ubuntu_ltp_syscalls - fallocate04, fallocate05, fdatasync03, fremovexattr01, fremovexattr02, fsync01, fsync04, fanotify15, msync04, preadv03, preadv03_64, preadv203, preadv203_64, pwritev03, pwritev03_64, sync03, syncfs01, sync_file_range02, copy_file_range01, statx04 (bug 1842266) fsetxattr01, fgetxattr01, fanotify13, fanotify14, lremovexattr01, setxattr01 (bug 1842266)
  ubuntu_lttng_smoke_test - failed to build lttng module on 5.3 Bionic (bug 1844764)
  ubuntu_qrt_kernel_security - test_140_kernel_modules_not_tainted (bug 1850888)
  ubuntu_sysdig_smoke_test - failed to build sysdig DKMS with 5.3 kernel (bug 1844766)
  ubuntu_xfstests_btrfs - generic/430 time out
  ubuntu_xfstests_ext4 - generic/430 time out

5.3.0-21.22~18.04.1 - generic
Regression test CMPL, RTB.

Issue to note in amd64:
  ubuntu_bpf - test_maps failed with BTF is required (bug 1850123)
  ubuntu_kernel_selftests - psock_snd in net (bug 1812618)
  ubuntu_ltp - proc01 (bug 1829849) fs_fill (bug 1842266) vma05 (bug 1845863) memcg_max_usage_in_bytes (bug 1829979) memcg_stat (bug 1829983) memcg_use_hierarchy (bug 1829989) memcg_usage_in_bytes (bug 1829984) cpuset_hotplug (bug 1834006) getaddrinfo_01 (bug 1829995) crypto_user02 (bug 1837543)
  ubuntu_ltp_syscalls - fa...

Read more...

tags: added: regression-testing-passed
description: updated
description: updated
tags: removed: block-proposed-bionic
tags: removed: block-proposed
description: updated
description: updated
description: updated
Launchpad Janitor (janitor) wrote :
Download full text (53.6 KiB)

This bug was fixed in the package linux-hwe-edge - 5.3.0-22.24~18.04.1

---------------
linux-hwe-edge (5.3.0-22.24~18.04.1) bionic; urgency=medium

  [ Ubuntu: 5.3.0-22.24 ]

  * [REGRESSION] md/raid0: cannot assemble multi-zone RAID0 with default_layout
    setting (LP: #1849682)
    - Revert "md/raid0: avoid RAID0 data corruption due to layout confusion."
  * refcount underflow and type confusion in shiftfs (LP: #1850867) // CVE-2019-15793
    - SAUCE: shiftfs: Correct id translation for lower fs operations
    - SAUCE: shiftfs: prevent type confusion
    - SAUCE: shiftfs: Fix refcount underflow in btrfs ioctl handling
  * CVE-2018-12207
    - kvm: x86, powerpc: do not allow clearing largepages debugfs entry
    - SAUCE: KVM: vmx, svm: always run with EFER.NXE=1 when shadow paging is
      active
    - SAUCE: x86: Add ITLB_MULTIHIT bug infrastructure
    - SAUCE: kvm: mmu: ITLB_MULTIHIT mitigation
    - SAUCE: kvm: Add helper function for creating VM worker threads
    - SAUCE: kvm: x86: mmu: Recovery of shattered NX large pages
    - SAUCE: cpu/speculation: Uninline and export CPU mitigations helpers
    - SAUCE: kvm: x86: mmu: Apply global mitigations knob to ITLB_MULTIHIT
  * CVE-2019-11135
    - x86/msr: Add the IA32_TSX_CTRL MSR
    - x86/cpu: Add a helper function x86_read_arch_cap_msr()
    - x86/cpu: Add a "tsx=" cmdline option with TSX disabled by default
    - x86/speculation/taa: Add mitigation for TSX Async Abort
    - x86/speculation/taa: Add sysfs reporting for TSX Async Abort
    - kvm/x86: Export MDS_NO=0 to guests when TSX is enabled
    - x86/tsx: Add "auto" option to the tsx= cmdline parameter
    - x86/speculation/taa: Add documentation for TSX Async Abort
    - x86/tsx: Add config options to set tsx=on|off|auto
    - [Config] Disable TSX by default when possible
  * CVE-2019-0154
    - SAUCE: drm/i915: Lower RM timeout to avoid DSI hard hangs
    - SAUCE: drm/i915/gen8+: Add RC6 CTX corruption WA
  * CVE-2019-0155
    - SAUCE: drm/i915: Rename gen7 cmdparser tables
    - SAUCE: drm/i915: Disable Secure Batches for gen6+
    - SAUCE: drm/i915: Remove Master tables from cmdparser
    - SAUCE: drm/i915: Add support for mandatory cmdparsing
    - SAUCE: drm/i915: Support ro ppgtt mapped cmdparser shadow buffers
    - SAUCE: drm/i915: Allow parsing of unsized batches
    - SAUCE: drm/i915: Add gen9 BCS cmdparsing
    - SAUCE: drm/i915/cmdparser: Use explicit goto for error paths
    - SAUCE: drm/i915/cmdparser: Add support for backward jumps
    - SAUCE: drm/i915/cmdparser: Ignore Length operands during command matching

linux-hwe-edge (5.3.0-21.22~18.04.1) bionic; urgency=medium

  * bionic/linux-hwe-edge: 5.3.0-21.22~18.04.1 -proposed tracker (LP: #1850485)

  [ Ubuntu: 5.3.0-21.22 ]

  * eoan/linux: 5.3.0-21.22 -proposed tracker (LP: #1850486)
  * Fix signing of staging modules in eoan (LP: #1850234)
    - [Packaging] Leave unsigned modules unsigned after adding .gnu_debuglink

linux-hwe-edge (5.3.0-20.21~18.04.1) bionic; urgency=medium

  * bionic/linux-hwe-edge: 5.3.0-20.21~18.04.1 -proposed tracker (LP: #1849063)

  * Eoan update: 5.3.7 upstream stable release (LP: #1848750)
    - [Config] Remove Rio500
    - [Config...

Changed in linux-hwe-edge (Ubuntu Bionic):
status: Confirmed → Fix Released
Harm van Bakel (hvbakel) wrote :

Neither kernel 5.3.0-21 nor 5.3.0-22 will boot for me on a Dell Precision 5720 AIO system. The system will drop to a BusyBox prompt with an error message that the UUID specified in fstab does not exist. Last successful boot is on 5.3.0-19.

Andy Whitcroft (apw) on 2019-11-13
tags: removed: kernel-sru-backport-of-1850486
description: updated
tags: removed: kernel-release-tracking-bug-live
Changed in kernel-sru-workflow:
status: In Progress → Invalid
Changed in linux-hwe-edge (Ubuntu Bionic):
status: Fix Released → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers