jammy/linux-gkeop: 5.15.0-1029.34 -proposed tracker

Bug #2033793 reported by Stefan Bader
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Kernel SRU Workflow
Fix Released
Medium
Roxana Nicolescu
Abi-testing
New
Undecided
Unassigned
Automated-testing
Fix Released
Medium
Canonical Kernel Team
Boot-testing
Fix Released
Medium
Unassigned
Certification-testing
Invalid
Medium
Unassigned
New-review
Fix Released
Medium
Andy Whitcroft
Prepare-package
Fix Released
Medium
Roxana Nicolescu
Prepare-package-generate
Fix Released
Medium
Roxana Nicolescu
Prepare-package-meta
Fix Released
Medium
Roxana Nicolescu
Prepare-package-signed
Fix Released
Medium
Roxana Nicolescu
Promote-signing-to-proposed
Invalid
Medium
Unassigned
Promote-to-proposed
Fix Released
Medium
Ubuntu Stable Release Updates Team
Promote-to-security
New
Medium
Ubuntu Stable Release Updates Team
Promote-to-updates
New
Medium
Ubuntu Stable Release Updates Team
Regression-testing
Incomplete
Medium
Canonical Kernel Team
Security-signoff
In Progress
Medium
Steve Beattie
Sru-review
Fix Released
Medium
Andy Whitcroft
Verification-testing
Fix Released
Medium
Canonical Kernel Team
canonical-signing-jobs
Task00
Fix Released
Medium
Andy Whitcroft
linux-gkeop (Ubuntu)
Jammy
Fix Released
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 --
built:
  from: 26d1f99c09535141
  route-entry: 1
delta:
  promote-to-proposed: [main, meta, signed, generate]
flag:
  boot-testing-requested: true
  bugs-spammed: true
  proposed-announcement-sent: true
  proposed-testing-requested: true
  stream-from-cycle: true
issue: KSRU-9578
kernel-stable-master-bug: 2033821
packages:
  generate: linux-generate-gkeop
  main: linux-gkeop
  meta: linux-meta-gkeop
  signed: linux-signed-gkeop
phase: Testing
phase-changed: Saturday, 16. September 2023 01:46 UTC
reason:
  regression-testing: Stalled -s testing FAILED
  security-signoff: Stalled -s waiting for signoff
synthetic:
  :promote-to-as-proposed: Fix Released
trackers:
  focal/linux-gkeop-5.15: bug 2033792
variant: debs
versions:
  main: 5.15.0-1029.34
  meta: 5.15.0.1029.28
  signed: 5.15.0-1029.34
~~:
  announce:
    swm-transition-crankable: 2023-09-14 16:25:54.472997
  clamps:
    new-review: 26d1f99c09535141
    promote-to-proposed: 26d1f99c09535141
    self: 5.15.0-1029.34
    sru-review: 26d1f99c09535141

Stefan Bader (smb)
tags: added: kernel-release-tracking-bug-live
description: updated
tags: added: kernel-sru-cycle-2023.09.04-1
description: updated
tags: added: kernel-sru-derivative-of-2033821
Changed in kernel-sru-workflow:
status: New → Confirmed
importance: Undecided → Medium
Changed in linux-gkeop (Ubuntu Jammy):
importance: Undecided → Medium
Changed in kernel-sru-workflow:
status: Confirmed → Triaged
description: updated
Changed in kernel-sru-workflow:
status: Triaged → In Progress
tags: added: kernel-jira-issue-ksru-9578
description: updated
description: updated
description: updated
description: updated
description: updated
description: updated
description: updated
description: updated
description: updated
description: updated
description: updated
Changed in kernel-sru-workflow:
assignee: nobody → Roxana Nicolescu (roxanan)
summary: - jammy/linux-gkeop: <version to be filled> -proposed tracker
+ jammy/linux-gkeop: 5.15.0-1029.34 -proposed tracker
description: updated
description: updated
description: updated
Revision history for this message
Roxana Nicolescu (roxanan) wrote :

So, I noticed some things. First, control.stub file was pushed, I removed that.
Second, ./update-dkms-version was probably never called, some dkms module would need to be dropped. To avoid causing an explosion, I decided to just revert that and keep it the same, but I need to investigate if these modules are actually needed or not. If yes, we need to update kernel-version repo for this kernels with better mappings. Joseph noticed the same thing for jammy:gke.
I did a build on cbd and it succeeded. Fingers crossed, this is fine.

description: updated
description: updated
description: updated
description: updated
description: updated
description: updated
description: updated
description: updated
description: updated
description: updated
description: updated
description: updated
description: updated
description: updated
description: updated
description: updated
description: updated
description: updated
description: updated
description: updated
description: updated
Changed in kernel-sru-workflow:
status: In Progress → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :
Download full text (57.2 KiB)

This bug was fixed in the package linux-gkeop - 5.15.0-1030.35

---------------
linux-gkeop (5.15.0-1030.35) jammy; urgency=medium

  * jammy/linux-gkeop: 5.15.0-1030.35 -proposed tracker (LP: #2036544)

  [ Ubuntu: 5.15.0-86.96 ]

  * jammy/linux: 5.15.0-86.96 -proposed tracker (LP: #2036575)
  * 5.15.0-85 live migration regression (LP: #2036675)
    - Revert "KVM: x86: Always enable legacy FP/SSE in allowed user XFEATURES"
    - Revert "x86/kvm/fpu: Limit guest user_xfeatures to supported bits of XCR0"
  * Regression for ubuntu_bpf test build on Jammy 5.15.0-85.95 (LP: #2035181)
    - selftests/bpf: fix static assert compilation issue for test_cls_*.c
  * `refcount_t: underflow; use-after-free.` on hidon w/ 5.15.0-85-generic
    (LP: #2034447)
    - crypto: rsa-pkcs1pad - Use helper to set reqsize

linux-gkeop (5.15.0-1029.34) jammy; urgency=medium

  * jammy/linux-gkeop: 5.15.0-1029.34 -proposed tracker (LP: #2033793)

  * CVE-2023-20569
    - Ubuntu: [Config] gkeop: enable Speculative Return Stack Overflow mitigation

  * Jammy update: v5.15.118 upstream stable release (LP: #2030239)
    - [Config] gkeop: updateconfigs for DECNET

  * Jammy update: v5.15.117 upstream stable release (LP: #2030107)
    - [Config] gkeop: updateconfigs for BLK_DEV_SX8

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

  [ Ubuntu: 5.15.0-85.95 ]

  * jammy/linux: 5.15.0-85.95 -proposed tracker (LP: #2033821)
  * Please enable Renesas RZ platform serial installer (LP: #2022361)
    - [Config] enable hihope RZ/G2M serial console
    - [Config] Mark sh-sci as built-in
  * Request backport of xen timekeeping performance improvements (LP: #2033122)
    - x86/xen/time: prefer tsc as clocksource when it is invariant
  * kdump doesn't work with UEFI secure boot and kernel lockdown enabled on
    ARM64 (LP: #2033007)
    - [Config]: Enable CONFIG_KEXEC_IMAGE_VERIFY_SIG
    - kexec, KEYS: make the code in bzImage64_verify_sig generic
    - arm64: kexec_file: use more system keyrings to verify kernel image signature
  * ubuntu_kernel_selftests:net:vrf-xfrm-tests.sh: 8 failed test cases on
    jammy/fips (LP: #2019880)
    - selftests: net: vrf-xfrm-tests: change authentication and encryption algos
  * ubuntu_kernel_selftests:net:tls: 88 failed test cases on jammy/fips
    (LP: #2019868)
    - selftests/harness: allow tests to be skipped during setup
    - selftests: net: tls: check if FIPS mode is enabled
  * A general-proteciton exception during guest migration to unsupported PKRU
    machine (LP: 2032164, reverted)
    - x86/kvm/fpu: Limit guest user_xfeatures to supported bits of XCR0
    - KVM: x86: Always enable legacy FP/SSE in allowed user XFEATURES
  * CVE-2023-4569
    - netfilter: nf_tables: deactivate catchall elements in next generation
  * CVE-2023-20569
    - x86/cpu, kvm: Add support for CPUID_80000021_EAX
    - x86/srso: Add a Speculative RAS Overflow mitigation
    - x86/srso: Add IBPB_BRTYPE support
    - x86/srso: Add SRSO_NO support
    - x86/srso: Add IBPB
    - x86/srso: Add IBPB on VMEXIT
    - x86/srso: Fix return thunks in generated code
    - x86/srso: Tie SBPB bit setting to microcode patch detection
    - x86: fix ba...

Changed in linux-gkeop (Ubuntu Jammy):
status: New → Fix Released
Changed in kernel-sru-workflow:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.