jammy/linux: 5.15.0-30.31 -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 --
boot-testing-requested: true
bugs-spammed: true
built:
  from: 65b6f9c450a46e44
  route-entry: 1
delta:
  promote-to-proposed:
  - lrs
  - main
  - meta
  - signed
  - lrm
  - lrg
  promote-to-updates:
  - meta
  - main
  - lrs
  - lrm
  - signed
  sru-review:
  - main
  - lrs
  - meta
  - lrg
  - signed
  - lrm
issue: KSRU-1948
packages:
  lrg: linux-restricted-generate
  lrm: linux-restricted-modules
  lrs: linux-restricted-signatures
  main: linux
  meta: linux-meta
  signed: linux-signed
phase: Complete
phase-changed: Thursday, 12. May 2022 13:11 UTC
proposed-announcement-sent: true
proposed-testing-requested: true
reason: {}
synthetic:
  :promote-to-as-proposed: Fix Released
trackers:
  jammy/linux-gke: bug 1971641
  jammy/linux-lowlatency: bug 1971684
  jammy/linux-uc22: bug 1971681
variant: debs
versions:
  lrm: 5.15.0-30.31
  main: 5.15.0-30.31
  meta: 5.15.0.30.33
  signed: 5.15.0-30.31
~~:
  clamps:
    promote-to-proposed: 65b6f9c450a46e44
    self: 5.15.0-30.31
    sru-review: 65b6f9c450a46e44

[Stefan Bader (smb)]

Majority of boot tests were ok, this is a much smaller delta and was included in previous spins. And there is no time.

[Devices Certification Bot (ce-certification-qa)]

Kernel deb testing completes, no regressions found. Ready for Updates. Results here: https://trello.com/c/c0KUH7JT/2497-jammy-linux-image-5150-30-generic-5150-3031

[Stefan Bader (smb)]

Regression testing does not provide much additional information. There would be systems under test with ADT and CT which do not have AMX. And it is doubtful that any of the systems we have in RT do have it (not even sure there is ANY HW with it sold already).

[Stefan Bader (smb)]

No regressions were found in ADT and CT. Can be released.

[Launchpad Janitor (janitor)]

This bug was fixed in the package linux - 5.15.0-30.31

---------------
linux (5.15.0-30.31) jammy; urgency=medium

  * jammy/linux: 5.15.0-30.31 -proposed tracker (LP: #1971685)

  * Packaging resync (LP: #1786013)
    - [Packaging] update variants
    - debian/dkms-versions -- update from kernel-versions (main/2022.04.18)

  * Intel: enable x86 AMX (LP: #1967750)
    - x86/extable: Tidy up redundant handler functions
    - x86/extable: Get rid of redundant macros
    - x86/mce: Deduplicate exception handling
    - x86/mce: Get rid of stray semicolons
    - x86/extable: Rework the exception table mechanics
    - x86/extable: Provide EX_TYPE_DEFAULT_MCE_SAFE and EX_TYPE_FAULT_MCE_SAFE
    - x86/copy_mc: Use EX_TYPE_DEFAULT_MCE_SAFE for exception fixups
    - x86/fpu: Use EX_TYPE_FAULT_MCE_SAFE for exception fixups
    - x86/extable: Remove EX_TYPE_FAULT from MCE safe fixups
    - x86/fpu/signal: Clarify exception handling in restore_fpregs_from_user()
    - x86/fpu/signal: Move header zeroing out of xsave_to_user_sigframe()
    - x86/fpu/signal: Move xstate clearing out of copy_fpregs_to_sigframe()
    - x86/fpu/signal: Change return type of copy_fpstate_to_sigframe() to boolean
    - x86/fpu/signal: Change return type of copy_fpregs_to_sigframe() helpers to
      boolean
    - x86/signal: Change return type of restore_sigcontext() to boolean
    - x86/fpu/signal: Change return type of fpu__restore_sig() to boolean
    - x86/fpu/signal: Change return type of __fpu_restore_sig() to boolean
    - x86/fpu/signal: Change return code of check_xstate_in_sigframe() to boolean
    - x86/fpu/signal: Change return code of restore_fpregs_from_user() to boolean
    - x86/fpu/signal: Fix missed conversion to correct boolean retval in
      save_xstate_epilog()
    - x86/fpu: Remove pointless argument from switch_fpu_finish()
    - x86/fpu: Update stale comments
    - x86/pkru: Remove useless include
    - x86/fpu: Restrict xsaves()/xrstors() to independent states
    - x86/fpu: Cleanup the on_boot_cpu clutter
    - x86/fpu: Remove pointless memset in fpu_clone()
    - x86/process: Clone FPU in copy_thread()
    - x86/fpu: Do not inherit FPU context for kernel and IO worker threads
    - x86/fpu: Cleanup xstate xcomp_bv initialization
    - x86/fpu/xstate: Provide and use for_each_xfeature()
    - x86/fpu/xstate: Mark all init only functions __init
    - x86/fpu: Move KVMs FPU swapping to FPU core
    - x86/fpu: Replace KVMs home brewed FPU copy from user
    - x86/fpu: Rework copy_xstate_to_uabi_buf()
    - x86/fpu: Mark fpu__init_prepare_fx_sw_frame() as __init
    - x86/fpu: Move context switch and exit to user inlines into sched.h
    - x86/fpu: Clean up CPU feature tests
    - x86/fpu: Make os_xrstor_booting() private
    - x86/fpu: Move os_xsave() and os_xrstor() to core
    - x86/fpu: Move legacy ASM wrappers to core
    - x86/fpu: Make WARN_ON_FPU() private
    - x86/fpu: Move fpregs_restore_userregs() to core
    - x86/fpu: Move mxcsr related code to core
    - x86/fpu: Move fpstate functions to api.h
    - x86/fpu: Remove internal.h dependency from fpu/signal.h
    - x86/sev: Include fpu/xcr.h
    - x86/fpu: Mop up the internal.h leftovers
    - ...

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

All tasks have been completed and the bug is being set to Fix Released