kinetic/linux-raspi: 5.19.0-1004.10 -proposed tracker

[Juerg Haefliger]

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: 2177304ca9af5457
  route-entry: 2
delta:
  promote-to-proposed: [main]
  promote-to-release: [main, meta]
flag:
  boot-testing-requested: true
  proposed-announcement-sent: true
  proposed-testing-requested: true
kernel-stable-master-bug: 1992639
packages:
  main: linux-raspi
  meta: linux-meta-raspi
phase: Complete
phase-changed: Tuesday, 18. October 2022 13:31 UTC
reason: {}
synthetic:
  :promote-to-as-proposed: Fix Released
variant: debs
versions:
  main: 5.19.0-1004.10
  meta: 5.19.0.1004.6
~~:
  clamps:
    new-review: 2177304ca9af5457
    promote-to-proposed: 2177304ca9af5457
    self: 5.19.0-1004.10
    sru-review: 2177304ca9af5457

[Juerg Haefliger (juergh)]

Basic boot tests passed on all Pis for both arm64 and armhf.

[Juerg Haefliger (juergh)]

RT tests passed locally on a Pi 4B 2GB.

[Juerg Haefliger (juergh)]

ADT tests for armhf all passed. Failed/missed arm64 results are due to the on-going ACPI reboot issue. Results from the previous run (5.19.0-1004.8) can be reused since it's the same source, just recompiled.

[Launchpad Janitor (janitor)]

This bug was fixed in the package linux-raspi - 5.19.0-1004.10

---------------
linux-raspi (5.19.0-1004.10) kinetic; urgency=medium

  * kinetic/linux-raspi: 5.19.0-1004.10 -proposed tracker (LP: #1993133)

  * armhf kernel compiled with gcc-12 fails to boot on pi 3/2 (LP: #1993120)
    - [Packaging] raspi: Use gcc-11 for armhf
    - [Config] raspi: updateconfigs for gcc-11 for armhf

  [ Ubuntu: 5.19.0-21.21 ]

  * kinetic/linux: 5.19.0-21.21 -proposed tracker (LP: #1992639)
  * cannot change mount namespace (LP: #1991691)
    - SAUCE: apparmor: Fix getaatr mediation causing snap failures
  * Kernel regresses openjdk on riscv64 (LP: #1992484)
    - SAUCE: Revert "riscv: mmap with PROT_WRITE but no PROT_READ is invalid"

  [ Ubuntu: 5.19.0-20.20 ]

  * kinetic/linux: 5.19.0-20.20 -proposed tracker (LP: #1992408)
  * Packaging resync (LP: #1786013)
    - debian/dkms-versions -- update from kernel-versions (main/master)
  * Kinetic kernels 5.19.0-18/19-generic won't boot on Intel 11th/12th gen
    (LP: #1991704)
    - drm/i915: fix null pointer dereference
  * rcu_sched detected stalls on CPUs/tasks (LP: #1967130)
    - [Config] Disable VMAP_STACK on riscv64
  * Disable sv57 as the userspace is not ready (LP: #1991790)
    - SAUCE: riscv: mm: Force disable sv57
  * earlyconsole prints question marks on 5.19.0-1002-generic (LP: #1988984)
    - [Config] Set CONFIG_PWM_SIFIVE=m for riscv64
  * RCU stalls (LP: #1991951)
    - [Config] Harmonize RCU_CPU_STALL_TIMEOUT
  * backport dkms fixes to build modules correctly for hwe-5.19+ kernels with
    custom compiler (LP: #1991664)
    - [Packaging] use versioned gcc-12
    - [Packaging] Update configs with versioned compiler version
  * FTBFS on kinetic (LP: #1990964)
    - SAUCE: uapi: Fixup strace compile error
  * CVE-2022-40768
    - scsi: stex: Properly zero out the passthrough command structure
  * [22.10 FEAT] zKVM: Crypto Passthrough Hotplug - kernel part (LP: #1852741)
    - s390/vfio-ap: use new AP bus interface to search for queue devices
    - s390/vfio-ap: move probe and remove callbacks to vfio_ap_ops.c
    - s390/vfio-ap: manage link between queue struct and matrix mdev
    - s390/vfio-ap: introduce shadow APCB
    - s390/vfio-ap: refresh guest's APCB by filtering AP resources assigned to
      mdev
    - s390/vfio-ap: allow assignment of unavailable AP queues to mdev device
    - s390/vfio-ap: rename matrix_dev->lock mutex to matrix_dev->mdevs_lock
    - s390/vfio-ap: introduce new mutex to control access to the KVM pointer
    - s390/vfio-ap: use proper locking order when setting/clearing KVM pointer
    - s390/vfio-ap: prepare for dynamic update of guest's APCB on assign/unassign
    - s390/vfio-ap: prepare for dynamic update of guest's APCB on queue
      probe/remove
    - s390/vfio-ap: allow hot plug/unplug of AP devices when assigned/unassigned
    - s390/vfio-ap: hot plug/unplug of AP devices when probed/removed
    - s390/vfio-ap: reset queues after adapter/domain unassignment
    - s390/vfio-ap: implement in-use callback for vfio_ap driver
    - s390/vfio-ap: sysfs attribute to display the guest's matrix
    - s390/vfio-ap: handle config changed and scan complete notification...

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

All tasks have been completed and the bug is being closed