Commit 18dfd1cbf6a6 for kernel

commit 18dfd1cbf6a633c39256c76ca13114de46435e22
Merge: 072c0b4f0f95 f4ea8e05f2a8
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Sat Dec 20 11:34:37 2025 -0800

    Merge tag 'arm64-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux

    Pull arm64 fixes from Catalin Marinas:
     "Two left-over updates that could not go into -rc1 due to conflicts
      with other series:

       - Simplify checks in arch_kfence_init_pool() since
         force_pte_mapping() already takes BBML2-noabort (break-before-make
         Level 2 with no aborts generated) into account

       - Remove unneeded SVE/SME fallback preserve/store handling in the
         arm64 EFI. With the recent updates, the fallback path is only taken
         for EFI runtime calls from hardirq or NMI contexts. In practice,
         this only happens under panic/oops/emergency_restart() and no
         restoring of the user state expected.

         There's a corresponding lkdtm update to trigger a BUG() or panic()
         from hardirq context together with a fixup not to confuse
         clang/objtool about the control flow

      GCS (guarded control stacks) fix: flush the GCS locking state on exec,
      otherwise the new task will not be able to enable GCS (locked as
      disabled)"

    * tag 'arm64-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux:
      lkdtm/bugs: Do not confuse the clang/objtool with busy wait loop
      arm64/gcs: Flush the GCS locking state on exec
      arm64/efi: Remove unneeded SVE/SME fallback preserve/store handling
      lkdtm/bugs: Add cases for BUG and PANIC occurring in hardirq context
      arm64: mm: Simplify check in arch_kfence_init_pool()