jammy/linux-ibm: 5.15.0-1014.16 -proposed tracker

Bug #1987750 reported by Stefan Bader
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Kernel SRU Workflow
Fix Committed
Medium
Unassigned
Automated-testing
Invalid
Medium
Canonical Kernel Team
Boot-testing
Invalid
Medium
Unassigned
Certification-testing
Invalid
Medium
Unassigned
New-review
Invalid
Medium
Andy Whitcroft
Prepare-package
Invalid
Medium
Khaled El Mously
Prepare-package-meta
Invalid
Medium
Khaled El Mously
Prepare-package-signed
Invalid
Medium
Khaled El Mously
Promote-signing-to-proposed
Invalid
Medium
Unassigned
Promote-to-proposed
Invalid
Medium
Ubuntu Stable Release Updates Team
Promote-to-security
Invalid
Medium
Ubuntu Stable Release Updates Team
Promote-to-updates
Invalid
Medium
Ubuntu Stable Release Updates Team
Regression-testing
Invalid
Medium
Canonical Kernel Team
Security-signoff
Invalid
Medium
Steve Beattie
Sru-review
Invalid
Medium
Andy Whitcroft
Verification-testing
Invalid
Medium
Canonical Kernel Team
linux-ibm (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: d088d3dc1dd4ec81
  route-entry: 1
delta:
  promote-to-proposed: [meta, signed, main]
flag:
  boot-testing-requested: true
  bugs-spammed: true
  proposed-announcement-sent: true
  proposed-testing-requested: true
issue: KSRU-4805
kernel-stable-master-bug: 1987775
packages:
  main: linux-ibm
  meta: linux-meta-ibm
  signed: linux-signed-ibm
phase: Testing
phase-changed: Wednesday, 21. September 2022 16:41 UTC
reason:
  regression-testing: Stalled -s testing FAILED
synthetic:
  :promote-to-as-proposed: Fix Released
variant: debs
versions:
  main: 5.15.0-1014.16
  meta: 5.15.0.1014.13
  signed: 5.15.0-1014.16
~~:
  clamps:
    new-review: d088d3dc1dd4ec81
    promote-to-proposed: d088d3dc1dd4ec81
    self: 5.15.0-1014.16
    sru-review: d088d3dc1dd4ec81

Stefan Bader (smb)
tags: added: kernel-release-tracking-bug-live
description: updated
tags: added: kernel-sru-cycle-2022.08.29-1
description: updated
tags: added: kernel-sru-derivative-of-1987775
Changed in kernel-sru-workflow:
status: New → Confirmed
importance: Undecided → Medium
Changed in linux-ibm (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-4805
description: updated
description: updated
summary: - jammy/linux-ibm: <version to be filled> -proposed tracker
+ jammy/linux-ibm: 5.15.0-1014.16 -proposed tracker
description: updated
description: updated
description: updated
description: updated
description: updated
description: updated
description: updated
description: updated
Andy Whitcroft (apw)
tags: added: kernel-signing-bot
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
tags: added: automated-testing-passed
description: updated
tags: removed: kernel-release-tracking-bug-live
Changed in kernel-sru-workflow:
status: In Progress → Invalid
Changed in linux-ibm (Ubuntu Jammy):
status: New → Invalid
Changed in kernel-sru-workflow:
status: Invalid → Fix Committed
Revision history for this message
Khaled El Mously (kmously) wrote :

This is a 0829 kernel that was cranked in the middle of the *0919* cycle so it was already very late, and only after more than a week later after all testing had finished did I notice that it is based on the 0919 Jammy base (5.15.0-49.55) not the 0829 Jammy base. At that point it is easier to discard it and just crank 0919.

Revision history for this message
Launchpad Janitor (janitor) wrote :
Download full text (84.2 KiB)

This bug was fixed in the package linux-ibm - 5.15.0-1015.17

---------------
linux-ibm (5.15.0-1015.17) jammy; urgency=medium

  * jammy/linux-ibm: 5.15.0-1015.17 -proposed tracker (LP: #1989760)

  [ Ubuntu: 5.15.0-50.56 ]

  * jammy/linux: 5.15.0-50.56 -proposed tracker (LP: #1990148)
  * CVE-2022-3176
    - io_uring: refactor poll update
    - io_uring: move common poll bits
    - io_uring: kill poll linking optimisation
    - io_uring: inline io_poll_complete
    - io_uring: correct fill events helpers types
    - io_uring: clean cqe filling functions
    - io_uring: poll rework
    - io_uring: remove poll entry from list when canceling all
    - io_uring: bump poll refs to full 31-bits
    - io_uring: fail links when poll fails
    - io_uring: fix wrong arm_poll error handling
    - io_uring: fix UAF due to missing POLLFREE handling
  * ip/nexthop: fix default address selection for connected nexthop
    (LP: #1988809)
    - selftests/net: test nexthop without gw
  * ip/nexthop: fix default address selection for connected nexthop
    (LP: #1988809) // icmp_redirect.sh in ubuntu_kernel_selftests failed on
    Jammy 5.15.0-49.55 (LP: #1990124)
    - ip: fix triggering of 'icmp redirect'

linux-ibm (5.15.0-1014.16) jammy; urgency=medium

  * jammy/linux-ibm: 5.15.0-1014.16 -proposed tracker (LP: #1987750)

  * Jammy update: v5.15.49 upstream stable release (LP: #1983149)
    - [config] Update configs for LIB_MEMNEQ

  [ Ubuntu: 5.15.0-49.55 ]

  * jammy/linux: 5.15.0-49.55 -proposed tracker (LP: #1989785)
  * amdgpu module crash after 5.15 kernel update (LP: #1981883)
    - drm/amdgpu: fix check in fbdev init
  * scsi: hisi_sas: Increase debugfs_dump_index after dump is  completed
    (LP: #1982070)
    - scsi: hisi_sas: Increase debugfs_dump_index after dump is completed
  * [UBUNTU 22.04] s390/qeth: cache link_info for ethtool (LP: #1984103)
    - s390/qeth: cache link_info for ethtool
  * WARN in trace_event_dyn_put_ref (LP: #1987232)
    - tracing/perf: Fix double put of trace event when init fails
  * Jammy update: v5.15.60 upstream stable release (LP: #1989221)
    - x86/speculation: Make all RETbleed mitigations 64-bit only
    - selftests/bpf: Extend verifier and bpf_sock tests for dst_port loads
    - selftests/bpf: Check dst_port only on the client socket
    - block: fix default IO priority handling again
    - tools/vm/slabinfo: Handle files in debugfs
    - ACPI: video: Force backlight native for some TongFang devices
    - ACPI: video: Shortening quirk list by identifying Clevo by board_name only
    - ACPI: APEI: Better fix to avoid spamming the console with old error logs
    - crypto: arm64/poly1305 - fix a read out-of-bound
    - KVM: x86: do not report a vCPU as preempted outside instruction boundaries
    - KVM: x86: do not set st->preempted when going back to user space
    - KVM: selftests: Make hyperv_clock selftest more stable
    - tools/kvm_stat: fix display of error when multiple processes are found
    - selftests: KVM: Handle compiler optimizations in ucall
    - KVM: x86/svm: add __GFP_ACCOUNT to __sev_dbg_{en,de}crypt_user()
    - arm64: set UXN on swapper page tables
    - btrfs: zoned: prevent allocation fro...

Changed in linux-ibm (Ubuntu Jammy):
status: Invalid → 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.