jammy/linux-intel-iot-realtime: 5.15.0-1021.26 -proposed tracker

[Stefan Bader]

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: 7f28f73600229924
  route-entry: 1
delta:
  promote-to-proposed: [signed, main, meta, generate]
  promote-to-updates: [meta, main, signed]
flag:
  boot-testing-requested: true
  proposed-announcement-sent: true
  proposed-testing-requested: true
  stream-from-cycle: true
issue: KSRU-6280
kernel-stable-master-bug: 2003439
packages:
  generate: linux-generate-intel-iot-realtime
  main: linux-intel-iot-realtime
  meta: linux-meta-intel-iot-realtime
  signed: linux-signed-intel-iot-realtime
phase: Complete
phase-changed: Wednesday, 08. March 2023 21:06 UTC
reason: {}
synthetic:
  :promote-to-as-proposed: Fix Released
trackers:
  jammy/linux-uc22-intel-iot-realtime: bug 2003435
variant: debs
versions:
  lrm: 5.15.0-1021.26
  main: 5.15.0-1021.26
  meta: 5.15.0.1021.27
  signed: 5.15.0-1021.26+2
~~:
  clamps:
    new-review: 7f28f73600229924
    promote-to-proposed: 7f28f73600229924
    self: 5.15.0-1021.26
    sru-review: 7f28f73600229924

[Andrea Righi (arighi)]

Secure boot / lockdown seems to work correctly with this kernel.

ubuntu@jammysecure:~$ uname -r
5.15.0-1021-intel-iot-realtime
ubuntu@jammysecure:~$ sudo dmesg | grep "secureboot"
[ 0.015437] secureboot: Secure boot enabled
ubuntu@jammysecure:~$ cat /sys/kernel/security/lockdown
none [integrity] confidentiality

[Jian Hui Lee (jianhuilee)]

currently there is no hardware for the cert testing, so set the status to invalid.

[Jian Hui Lee (jianhuilee)]

there are no bugs to be verified, so adding the verification-testing-passed tag.

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

All tasks have been completed and the bug is being closed