noble/linux-azure: 6.8.0-1001.1 -proposed tracker

Bug #2052777 reported by Andrea Righi
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Kernel SRU Workflow
Fix Released
Medium
Unassigned
Abi-testing
Fix Released
Medium
Unassigned
Automated-testing
Fix Released
Medium
Canonical Kernel Team
Boot-testing
Fix Released
Medium
Unassigned
New-review
Fix Released
Medium
Andy Whitcroft
Prepare-package
Fix Released
Medium
Andrea Righi
Prepare-package-generate
Fix Released
Medium
Andrea Righi
Prepare-package-lrg
Fix Released
Medium
Unassigned
Prepare-package-lrm
Fix Released
Medium
Andy Whitcroft
Prepare-package-lrs
Fix Released
Medium
Andy Whitcroft
Prepare-package-meta
Fix Released
Medium
Andrea Righi
Prepare-package-signed
Fix Released
Medium
Andrea Righi
Promote-signing-to-proposed
Invalid
Medium
Unassigned
Promote-to-proposed
Fix Released
Medium
Canonical Kernel Team
Promote-to-release
Fix Released
Medium
Ubuntu Package Archive Administrators
Regression-testing
Fix Released
Medium
Canonical Kernel Team
Signing-signoff
Fix Released
Undecided
Unassigned
Sru-review
Fix Released
Medium
Andy Whitcroft
canonical-signing-jobs
Task00
Fix Released
Medium
Andy Whitcroft
linux-azure (Ubuntu)
Noble
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: 6e916d3e37d2a3ca
  route-entry: 1
comments:
  abi-testing: 1
delta:
  promote-to-proposed: [lrm, lrs, lrg]
  promote-to-release: [lrm, lrs, main, meta, signed]
flag:
  boot-testing-requested: true
  proposed-announcement-sent: true
packages:
  generate: linux-generate-azure
  lrg: linux-restricted-generate-azure
  lrm: linux-restricted-modules-azure
  lrs: linux-restricted-signatures-azure
  main: linux-azure
  meta: linux-meta-azure
  signed: linux-signed-azure
phase: Complete
phase-changed: Saturday, 02. March 2024 19:11 UTC
reason: {}
synthetic:
  :promote-to-as-proposed: Fix Released
variant: debs
versions:
  lrm: 6.8.0-1001.1+4
  main: 6.8.0-1001.1
  meta: 6.8.0-1001.1
  signed: 6.8.0-1001.1
versions-replace:
  lrm: [6.8.0-1001.1]
~~:
  announce:
    swm-transition-crankable: 2024-02-13 09:31:15.455434
  clamps:
    new-review: 6e916d3e37d2a3ca
    promote-to-proposed: 6e916d3e37d2a3ca
    self: 6.8.0-1001.1
    sru-review: 6e916d3e37d2a3ca
  tracker:
    last-message: '2024-03-02 20:15:34.838671+00:00'

Andrea Righi (arighi)
tags: added: kernel-release-tracking-bug-live
description: updated
tags: added: kernel-sru-cycle-d2024.02.07-1
Changed in kernel-sru-workflow:
status: New → Confirmed
importance: Undecided → Medium
Changed in linux-azure (Ubuntu Noble):
importance: Undecided → Medium
tags: added: kernel-block-derivatives
Changed in kernel-sru-workflow:
status: Confirmed → Triaged
description: updated
Changed in kernel-sru-workflow:
status: Triaged → In Progress
description: updated
description: updated
description: updated
description: updated
Andrea Righi (arighi)
summary: - noble/linux-azure: <version to be filled> -proposed tracker
+ noble/linux-azure: 6.8.0-1001.1 -proposed tracker
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
Download full text (45.6 KiB)

amd64/azure canonical-certs.pem unchanged
amd64/azure canonical-revoked-certs.pem unchanged
amd64/azure fwinfo differs
  @@ -77,6 +77,7 @@
   firmware: amdgpu/dcn_3_1_6_dmcub.bin
   firmware: amdgpu/dcn_3_2_0_dmcub.bin
   firmware: amdgpu/dcn_3_2_1_dmcub.bin
  +firmware: amdgpu/dcn_3_5_dmcub.bin (ok)
   firmware: amdgpu/dimgrey_cavefish_ce.bin
   firmware: amdgpu/dimgrey_cavefish_dmcub.bin
   firmware: amdgpu/dimgrey_cavefish_me.bin
  @@ -120,6 +121,7 @@
   firmware: amdgpu/gc_11_0_0_mes_2.bin
   firmware: amdgpu/gc_11_0_0_pfp.bin
   firmware: amdgpu/gc_11_0_0_rlc.bin
  +firmware: amdgpu/gc_11_0_0_rlc_1.bin (ok)
   firmware: amdgpu/gc_11_0_0_toc.bin
   firmware: amdgpu/gc_11_0_1_imu.bin
   firmware: amdgpu/gc_11_0_1_me.bin
  @@ -153,6 +155,13 @@
   firmware: amdgpu/gc_11_0_4_mes_2.bin
   firmware: amdgpu/gc_11_0_4_pfp.bin
   firmware: amdgpu/gc_11_0_4_rlc.bin
  +firmware: amdgpu/gc_11_5_0_imu.bin (ok)
  +firmware: amdgpu/gc_11_5_0_me.bin (ok)
  +firmware: amdgpu/gc_11_5_0_mec.bin (ok)
  +firmware: amdgpu/gc_11_5_0_mes1.bin (ok)
  +firmware: amdgpu/gc_11_5_0_mes_2.bin (ok)
  +firmware: amdgpu/gc_11_5_0_pfp.bin (ok)
  +firmware: amdgpu/gc_11_5_0_rlc.bin (ok)
   firmware: amdgpu/gc_9_4_3_mec.bin
   firmware: amdgpu/gc_9_4_3_rlc.bin
   firmware: amdgpu/green_sardine_asd.bin
  @@ -442,7 +451,9 @@
   firmware: amdgpu/sienna_cichlid_vcn.bin
   firmware: amdgpu/smu_13_0_0.bin
   firmware: amdgpu/smu_13_0_10.bin
  +firmware: amdgpu/smu_13_0_6.bin (ok)
   firmware: amdgpu/smu_13_0_7.bin
  +firmware: amdgpu/smu_14_0_2.bin (ok)
   firmware: amdgpu/stoney_ce.bin
   firmware: amdgpu/stoney_me.bin
   firmware: amdgpu/stoney_mec.bin
  @@ -497,6 +508,7 @@
   firmware: amdgpu/vcn_4_0_2.bin
   firmware: amdgpu/vcn_4_0_3.bin
   firmware: amdgpu/vcn_4_0_4.bin
  +firmware: amdgpu/vcn_4_0_5.bin (ok)
   firmware: amdgpu/vega10_acg_smc.bin
   firmware: amdgpu/vega10_asd.bin
   firmware: amdgpu/vega10_cap.bin
  @@ -560,6 +572,7 @@
   firmware: amdgpu/verde_rlc.bin
   firmware: amdgpu/verde_smc.bin
   firmware: amdgpu/verde_uvd.bin
  +firmware: amdgpu/vpe_6_1_0.bin (ok)
   firmware: amdgpu/yellow_carp_ce.bin
   firmware: amdgpu/yellow_carp_dmcub.bin
   firmware: amdgpu/yellow_carp_me.bin
  @@ -614,6 +627,9 @@
   firmware: e100/d101m_ucode.bin
   firmware: e100/d101s_ucode.bin
   firmware: e100/d102e_ucode.bin
  +firmware: habanalabs/gaudi/gaudi-boot-fit.itb (ok)
  +firmware: habanalabs/gaudi/gaudi-fit.itb (ok)
  +firmware: habanalabs/gaudi/gaudi_tpc.bin (ok)
   firmware: hfi1_dc8051.fw
   firmware: hfi1_fabric.fw
   firmware: hfi1_pcie.fw
  @@ -647,6 +663,7 @@
   firmware: i915/kbl_guc_70.1.1.bin
   firmware: i915/kbl_huc_4.0.0.bin
   firmware: i915/mtl_dmc.bin
  +firmware: i915/mtl_gsc_1.bin (ok)
   firmware: i915/mtl_guc_70.bin
   firmware: i915/mtl_huc_gsc.bin
   firmware: i915...

description: updated
description: updated
description: updated
description: updated
description: updated
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Kernel requires additional signoff

New kernel with signed kernels; signing-review required.

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
Paolo Pisati (p-pisati) wrote :

amd64:
ubuntu@amd64-secureboot-testing:~$ uname -a
Linux amd64-secureboot-testing 6.8.0-1001-azure #1-Ubuntu SMP Tue Feb 13 17:53:47 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

ubuntu@amd64-secureboot-testing:~$ sudo dmesg | grep secure
[ 0.000000] secureboot: Secure boot enabled
[ 0.004354] secureboot: Secure boot enabled

ubuntu@amd64-secureboot-testing:~$ cat /sys/kernel/security/lockdown
none [integrity] confidentiality

Revision history for this message
Paolo Pisati (p-pisati) wrote :

arm64:
ubuntu@arm64-secureboot-testing:~$ uname -a
Linux arm64-secureboot-testing 6.8.0-1001-azure #1-Ubuntu SMP Tue Feb 13 23:14:13 UTC 2024 aarch64 aarch64 aarch64 GNU/Linux

ubuntu@arm64-secureboot-testing:~$ sudo dmesg | grep secure
[ 0.000000] secureboot: Secure boot enabled
[ 2.428098] ima: secureboot mode enabled

ubuntu@arm64-secureboot-testing:~$ cat /sys/kernel/security/lockdown
none [integrity] confidentiality

tags: added: automated-testing-passed regression-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
description: updated
description: updated
Andy Whitcroft (apw)
description: updated
description: updated
description: updated
description: updated
description: updated
description: updated
description: updated
Revision history for this message
Launchpad Janitor (janitor) wrote :
Download full text (49.8 KiB)

This bug was fixed in the package linux-azure - 6.8.0-1001.1

---------------
linux-azure (6.8.0-1001.1) noble; urgency=medium

  * noble/linux-azure: 6.8.0-1001.1 -proposed tracker (LP: #2052777)

  * Packaging resync (LP: #1786013)
    - debian.azure/dkms-versions -- update from kernel-versions (main/d2024.02.07)

  * Azure: cifs modules missing from the linux-modules package (LP: #2052980)
    - [Config] Move cifs.ko to linux-modules package

  * Azure: Enable CONFIG_TEST_LOCKUP (LP: #2052723)
    - [Config] CONFIG_TEST_LOCKUP=m

  * Miscellaneous Ubuntu changes
    - [Packaging] azure: update Rust toolchain
    - [Packaging] azure: move to kernel v6.8
    - [Config] azure: update annotations after moving to v6.8

  [ Ubuntu: 6.8.0-9.9 ]

  * noble/linux: 6.8.0-9.9 -proposed tracker (LP: #2052945)
  * Miscellaneous upstream changes
    - Revert "UBUNTU: [Packaging] temporarily disable Rust dependencies on
      riscv64"

  [ Ubuntu: 6.8.0-8.8 ]

  * noble/linux: 6.8.0-8.8 -proposed tracker (LP: #2052918)
  * Miscellaneous Ubuntu changes
    - [Packaging] riscv64: enable linux-libc-dev build
    - v6.8-rc4 rebase
  * Rebase on v6.8-rc4

  [ Ubuntu: 6.8.0-7.7 ]

  * noble/linux: 6.8.0-7.7 -proposed tracker (LP: #2052691)
  * update apparmor and LSM stacking patch set (LP: #2028253)
    - SAUCE: apparmor4.0.0 [01/87]: LSM stacking v39: integrity: disassociate
      ima_filter_rule from security_audit_rule
    - SAUCE: apparmor4.0.0 [02/87]: LSM stacking v39: SM: Infrastructure
      management of the sock security
    - SAUCE: apparmor4.0.0 [03/87]: LSM stacking v39: LSM: Add the lsmblob data
      structure.
    - SAUCE: apparmor4.0.0 [04/87]: LSM stacking v39: IMA: avoid label collisions
      with stacked LSMs
    - SAUCE: apparmor4.0.0 [05/87]: LSM stacking v39: LSM: Use lsmblob in
      security_audit_rule_match
    - SAUCE: apparmor4.0.0 [06/87]: LSM stacking v39: LSM: Add lsmblob_to_secctx
      hook
    - SAUCE: apparmor4.0.0 [07/87]: LSM stacking v39: Audit: maintain an lsmblob
      in audit_context
    - SAUCE: apparmor4.0.0 [08/87]: LSM stacking v39: LSM: Use lsmblob in
      security_ipc_getsecid
    - SAUCE: apparmor4.0.0 [09/87]: LSM stacking v39: Audit: Update shutdown LSM
      data
    - SAUCE: apparmor4.0.0 [10/87]: LSM stacking v39: LSM: Use lsmblob in
      security_current_getsecid
    - SAUCE: apparmor4.0.0 [11/87]: LSM stacking v39: LSM: Use lsmblob in
      security_inode_getsecid
    - SAUCE: apparmor4.0.0 [12/87]: LSM stacking v39: Audit: use an lsmblob in
      audit_names
    - SAUCE: apparmor4.0.0 [13/87]: LSM stacking v39: LSM: Create new
      security_cred_getlsmblob LSM hook
    - SAUCE: apparmor4.0.0 [14/87]: LSM stacking v39: Audit: Change context data
      from secid to lsmblob
    - SAUCE: apparmor4.0.0 [15/87]: LSM stacking v39: Netlabel: Use lsmblob for
      audit data
    - SAUCE: apparmor4.0.0 [16/87]: LSM stacking v39: LSM: Ensure the correct LSM
      context releaser
    - SAUCE: apparmor4.0.0 [17/87]: LSM stacking v39: LSM: Use lsmcontext in
      security_secid_to_secctx
    - SAUCE: apparmor4.0.0 [18/87]: LSM stacking v39: LSM: Use lsmcontext in
      security_lsmblob_to_secctx
    - SAUCE: ap...

Changed in linux-azure (Ubuntu Noble):
status: New → Fix Released
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
Changed in kernel-sru-workflow:
status: Fix Committed → Fix Released
description: updated
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.