)]}'
{
  "commit": "0435554a98c5c579c1ee22c2bce2630874c40c78",
  "tree": "02502a73d53a347e4a477cce2240a1e295228198",
  "parents": [
    "bd509fb1b6f48bcd5dd3e13ec36871336d77daa7"
  ],
  "author": {
    "name": "Ard Biesheuvel",
    "email": "ardb@kernel.org",
    "time": "Wed Nov 12 18:53:19 2025 +0100"
  },
  "committer": {
    "name": "Ard Biesheuvel",
    "email": "ardb@kernel.org",
    "time": "Sat Dec 06 19:57:34 2025 +0100"
  },
  "message": "arm64/efi: Remove unneeded SVE/SME fallback preserve/store handling\n\nSince commit 7137a203b251 (\"arm64/fpsimd: Permit kernel mode NEON with\nIRQs off\"), the only condition under which the fallback path is taken\nfor FP/SIMD preserve/restore across a EFI runtime call is when it is\ncalled from hardirq or NMI context.\n\nIn practice, this only happens when the EFI pstore driver is called to\ndump the kernel log buffer into a EFI variable under a panic, oops or\nemergency_restart() condition, and none of these can be expected to\nresult in a return to user space for the task in question.\n\nThis means that the existing EFI-specific logic for preserving and\nrestoring SVE/SME state is pointless, and can be removed.\n\nInstead, kill the task, so that an exceedingly unlikely inadvertent\nreturn to user space does not proceed with a corrupted FP/SIMD state.\nAlso, retain the preserve and restore of the base FP/SIMD state, as that\nmight belong to kernel mode use of FP/SIMD. (Note that EFI runtime calls\nare never invoked reentrantly, even in this case, and so any interrupted\nkernel mode FP/SIMD usage will be unrelated to EFI)\n\nSigned-off-by: Ard Biesheuvel \u003cardb@kernel.org\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "c154f72634e028ba41411f8222c35179321933d4",
      "old_mode": 33188,
      "old_path": "arch/arm64/kernel/fpsimd.c",
      "new_id": "9de1d8a604cbf2f7d0147a9322316856202e33c1",
      "new_mode": 33188,
      "new_path": "arch/arm64/kernel/fpsimd.c"
    }
  ]
}