jammy/linux-nvidia-6.5: 6.5.0-1019.19 -proposed tracker

Bug #2063578 reported by Stefan Bader
18
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Kernel SRU Workflow
Fix Committed
Medium
Unassigned
Abi-testing
Fix Released
Medium
Unassigned
Automated-testing
Invalid
Medium
Canonical Kernel Team
Boot-testing
Fix Released
Medium
Unassigned
Certification-testing
Invalid
Medium
Unassigned
New-review
Fix Released
Medium
Timo Aaltonen
Prepare-package
Fix Released
Medium
Jacob Martin
Prepare-package-generate
Fix Released
Medium
Jacob Martin
Prepare-package-lrg
Fix Released
Medium
Jacob Martin
Prepare-package-lrm
Fix Released
Medium
Jacob Martin
Prepare-package-lrs
Fix Released
Medium
Jacob Martin
Prepare-package-meta
Fix Released
Medium
Jacob Martin
Prepare-package-signed
Fix Released
Medium
Jacob Martin
Promote-signing-to-proposed
Invalid
Medium
Unassigned
Promote-to-proposed
Fix Released
Medium
Ubuntu Stable Release Updates Team
Promote-to-security
Fix Released
Medium
Andy Whitcroft
Promote-to-updates
Fix Released
Medium
Andy Whitcroft
Regression-testing
Fix Released
Medium
Canonical Kernel Team
Security-signoff
Fix Released
Medium
Rodrigo Figueiredo Zaiden
Sru-review
Fix Released
Medium
Andy Whitcroft
Verification-testing
Fix Released
Medium
Canonical Kernel Team
canonical-signing-jobs
Task00
Fix Released
Medium
Timo Aaltonen
linux-nvidia-6.5 (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: 3951a6062a20636f
  route-entry: 2
comments:
  abi-testing: 1
delta:
  promote-to-proposed: [lrm, lrs, main, meta, signed, lrg, generate]
  promote-to-security: []
  promote-to-updates: [lrm, lrs, main, meta, signed]
flag:
  boot-testing-requested: true
  bugs-spammed: true
  proposed-announcement-sent: true
  proposed-testing-requested: true
  stream-from-cycle: true
issue: KSRU-12137
kernel-stable-master-bug: 2063581
packages:
  generate: linux-generate-nvidia-6.5
  lrg: linux-restricted-generate-nvidia-6.5
  lrm: linux-restricted-modules-nvidia-6.5
  lrs: linux-restricted-signatures-nvidia-6.5
  main: linux-nvidia-6.5
  meta: linux-meta-nvidia-6.5
  signed: linux-signed-nvidia-6.5
phase: Complete
phase-changed: Tuesday, 14. May 2024 16:21 UTC
reason: {}
synthetic:
  :promote-to-as-proposed: Invalid
variant: debs
versions:
  lrm: 6.5.0-1019.19
  main: 6.5.0-1019.19
  meta: 6.5.0.1019.26
  signed: 6.5.0-1019.19
~~:
  announce:
    swm-transition-crankable: 2024-05-05 22:15:52.827099
  clamps:
    new-review: 3951a6062a20636f
    promote-to-proposed: 3951a6062a20636f
    self: 6.5.0-1019.19
    sru-review: 3951a6062a20636f
  tracker:
    last-message: '2024-05-14 07:27:16.322770+00:00'

Stefan Bader (smb)
tags: added: kernel-release-tracking-bug-live
description: updated
tags: added: kernel-sru-cycle-s2024.04.01-1
description: updated
tags: added: kernel-sru-backport-of-2063581
Changed in kernel-sru-workflow:
status: New → Confirmed
importance: Undecided → Medium
Changed in linux-nvidia-6.5 (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-12137
description: updated
description: updated
description: updated
description: updated
description: updated
description: updated
description: updated
description: updated
summary: - jammy/linux-nvidia-6.5: <version to be filled> -proposed tracker
+ jammy/linux-nvidia-6.5: 6.5.0-1019.19 -proposed tracker
description: updated
description: updated
description: updated
description: updated
description: updated
description: updated
description: updated
description: updated
description: updated
description: updated
Revision history for this message
Ubuntu Kernel Ancillary Bot (ubuntu-kernel-ancillary-bot) wrote : ABI testing

amd64/nvidia canonical-certs.pem unchanged
amd64/nvidia canonical-revoked-certs.pem unchanged
amd64/nvidia fwinfo unchanged
amd64/nvidia modules unchanged
amd64/nvidia retpoline unchanged
arm64/nvidia canonical-certs.pem unchanged
arm64/nvidia canonical-revoked-certs.pem unchanged
arm64/nvidia fwinfo unchanged
arm64/nvidia modules unchanged
arm64/nvidia retpoline unchanged
arm64/nvidia-64k canonical-certs.pem unchanged
arm64/nvidia-64k canonical-revoked-certs.pem unchanged
arm64/nvidia-64k fwinfo unchanged
arm64/nvidia-64k modules unchanged
arm64/nvidia-64k retpoline unchanged

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
description: updated
tags: added: boot-testing-passed
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
Revision history for this message
Jacob Martin (jacobmartin) wrote :

The only rt failure that stands out here is ftrace:test.d--filter--event-filter-function.tc in ubuntu_kselftests_ftrace. This fails on hinyari running 6.5.0-1019-nvidia-64k. Running this test on hinyari results in the same error on the previous kernel version 6.5.0-1018-nvidia-64k.

This is not a regression introduced by this new version of the kernel. The test both passes and fails on different runs for both kernel versions.

tags: added: regression-testing-passed
description: updated
description: updated
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package linux-nvidia-6.5 - 6.5.0-1019.19

---------------
linux-nvidia-6.5 (6.5.0-1019.19) jammy; urgency=medium

  * jammy/linux-nvidia-6.5: 6.5.0-1019.19 -proposed tracker (LP: #2063578)

  [ Ubuntu: 6.5.0-35.35 ]

  * mantic/linux: 6.5.0-35.35 -proposed tracker (LP: #2063581)
  * cifs: Copying file to same directory results in page fault (LP: #2060919)
    - SAUCE: Revert "cifs: fix flushing folio regression for 6.1 backport"
  * CVE-2024-26805
    - netlink: Fix kernel-infoleak-after-free in __skb_datagram_iter
  * CVE-2024-26801
    - Bluetooth: Avoid potential use-after-free in hci_error_reset
  * CVE-2024-26704
    - ext4: fix double-free of blocks due to wrong extents moved_len
  * CVE-2023-52601
    - jfs: fix array-index-out-of-bounds in dbAdjTree
  * CVE-2024-26635
    - llc: Drop support for ETH_P_TR_802_2.
  * CVE-2024-26622
    - tomoyo: fix UAF write bug in tomoyo_write_control()
  * CVE-2024-26614
    - tcp: make sure init the accept_queue's spinlocks once
    - ipv6: init the accept_queue's spinlocks in inet6_create
  * CVE-2024-52615
    - hwrng: core - Fix page fault dead lock on mmap-ed hwrng
  * CVE-2024-52602
    - jfs: fix slab-out-of-bounds Read in dtSearch
  * CVE-2023-47233
    - wifi: brcmfmac: Fix use-after-free bug in brcmf_cfg80211_detach
  * CVE-2024-2201
    - x86/bugs: Change commas to semicolons in 'spectre_v2' sysfs file
    - x86/syscall: Don't force use of indirect calls for system calls
    - x86/bhi: Add support for clearing branch history at syscall entry
    - x86/bhi: Define SPEC_CTRL_BHI_DIS_S
    - x86/bhi: Enumerate Branch History Injection (BHI) bug
    - x86/bhi: Add BHI mitigation knob
    - x86/bhi: Mitigate KVM by default
    - KVM: x86: Add BHI_NO
    - [Config] Set CONFIG_BHI to enabled (auto)

 -- Jacob Martin <email address hidden> Mon, 06 May 2024 13:26:26 -0500

Changed in linux-nvidia-6.5 (Ubuntu Jammy):
status: New → Fix Released
description: updated
description: updated
description: updated
description: updated
description: updated
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Workflow done!

All tasks have been completed and the bug is being closed

Changed in kernel-sru-workflow:
status: In Progress → Fix Committed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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