iv/linux
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
91b1ad0815
linux/arch/x86/platform/efi
History
Linus Torvalds f8566aa4f1 A single regression fix for x86: 
Moving the invocation of arch_cpu_finalize_init() earlier in the boot
   process caused a boot regression on IBT enabled system.
 
   The root cause is not the move of arch_cpu_finalize_init() itself. The
   system fails to boot because the subsequent efi_enter_virtual_mode() code
   has a non-IBT safe EFI call inside. This was never noticed because IBT
   was enabled after the EFI initialization.
 
   Switching the EFI call to use the IBT safe wrapper cures the problem.
 -----BEGIN PGP SIGNATURE-----
 
 iQJHBAABCgAxFiEEQp8+kY+LLUocC4bMphj1TA10mKEFAmSga0ITHHRnbHhAbGlu
 dXRyb25peC5kZQAKCRCmGPVMDXSYofPAEADCjJ40zgv7cbi6VTKudQhASwclWimy
 zJk1hR6u+Gt7slDAOS/lcHwPzwPB2wn9VsdTHClSHeJbdT3GBKMCOQOFaj1mHvOW
 e9H7PKUn76OLUSQtpquNiXvnkZGGK/FkTBCi1dEX3xhrWYQ9EVAg/9gDPLtCR5vv
 cS95KAETGq/7Krxdkgn/w1cav13t+WA25EjAochwG0DAiqVpj+QK1X+dvm8S9F4I
 MAyLboPK7cN7WijMVxruy1ho+n8L4ZHv6GcOnd9hD/Z6Tyk48hTvQOpVD7V3h1Yc
 GWzXVyOETuDAwBubfbxCFWQ2nbzwE6uCTGlwyaCmCxixxNSXhyiysvLOLgZr+tD9
 97/Z2tZM+nWjnL8vXvpVCKTNJHTssgh2GvUiKzecRuJWK/FoyfbiZllztVPewmRx
 k9hwf1qMzW8/XpcpfuY9XkfOBIPDUqWpKBtl9XpprU3EFOjEFfkNmdhGPFHkKefG
 v0LL3dc19f5N8/tFJN5mEww1ZolgQ0aIKqvT0CeY0x0MvCTT214OWb59tzrn+dw3
 tth+pGIZnh+5qM8geE1jQ162zkg+r0UaK4TClTqgwzrxIUHmBygI+LVnuPu2iYMi
 KlJSaOiU60NjzzVVujbSFclPIgkcINuVuQh5zyTGMBLtRgxPzARKTr8v9dqalHeH
 xcmDJsrKIpMy7A==
 =T/8G
 -----END PGP SIGNATURE-----

Merge tag 'x86-urgent-2023-07-01' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip

Pull x86 fix from Thomas Gleixner:
 "A single regression fix for x86:

  Moving the invocation of arch_cpu_finalize_init() earlier in the boot
  process caused a boot regression on IBT enabled system.

  The root cause is not the move of arch_cpu_finalize_init() itself. The
  system fails to boot because the subsequent efi_enter_virtual_mode()
  code has a non-IBT safe EFI call inside. This was not noticed before
  because IBT was enabled after the EFI initialization.

  Switching the EFI call to use the IBT safe wrapper cures the problem"

* tag 'x86-urgent-2023-07-01' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip:
  x86/efi: Make efi_set_virtual_address_map IBT safe
2023-07-01 11:40:01 -07:00
..
efi_32.c efi/x86: Move 32-bit code into efi_32.c 2020-08-20 11:18:36 +02:00
efi_64.c x86/efi: Make efi_set_virtual_address_map IBT safe 2023-06-30 15:26:24 +02:00
efi_stub_32.S x86: Prepare asm files for straight-line-speculation 2021-12-08 12:25:37 +01:00
efi_stub_64.S x86: Prepare asm files for straight-line-speculation 2021-12-08 12:25:37 +01:00
efi_thunk_64.S efi/x86-mixed: move unmitigated RET into .rodata 2022-08-16 09:28:05 +02:00
efi.c efi: Add unaccepted memory support 2023-06-06 17:22:20 +02:00
fake_mem.c efi: memmap: Move EFI fake memmap support into x86 arch tree 2022-11-18 09:14:09 +01:00
Makefile efi: x86: Move EFI runtime map sysfs code to arch/x86 2022-11-18 09:14:09 +01:00
memmap.c efi: xen: Set EFI_PARAVIRT for Xen dom0 boot on all architectures 2022-11-18 09:14:09 +01:00
quirks.c efivarfs: expose used and total size 2023-05-17 18:21:34 +02:00
runtime-map.c efi: x86: make kobj_type structure constant 2023-05-10 19:00:40 +02:00