diff options
| author | Ard Biesheuvel <ardb@kernel.org> | 2026-10-09 16:48:15 +0200 |
|---|---|---|
| committer | Ard Biesheuvel <ardb@kernel.org> | 2026-10-10 09:56:40 +0200 |
| commit | 191c12e9a71687b61d3298ac1e0d0d7298d103f0 (patch) | |
| tree | 1095eaaa029e8792b7735afcb033f0c3cf7797be /tools/perf/scripts/python/stackcollapse.py | |
| parent | 305c21908278e8417c16399b99f64e1729916a85 (diff) | |
| download | linux-next-191c12e9a71687b61d3298ac1e0d0d7298d103f0.tar.gz linux-next-191c12e9a71687b61d3298ac1e0d0d7298d103f0.zip | |
efi/runtime-wrappers: Don't park the worker after a recovered firmware fault
Commit 4b2c033b5bc9 ("efi/runtime-wrappers: retire the worker if a wedged
call ever returns") parks the efi_rts_wq worker instead of completing the
call if EFI runtime services have been disabled by the time the firmware
returns. The assumption is that this only happens if __efi_queue_work()
has given up waiting for the call.
However, arm64 also disables EFI runtime services when it recovers from a
synchronous exception taken by the firmware: efi_runtime_fixup_exception()
clears EFI_RUNTIME_SERVICES and unwinds the call so that it returns
EFI_ABORTED to efi_call_rts(), while the caller is still waiting for the
completion. The worker now parks without signalling it, so the caller is
stuck for the full EFI_RTS_TIMEOUT of 120 seconds, after which it reports
that the firmware is wedged, which is misleading.
x86 is not affected, as it signals the completion from its page fault
handler before parking the worker.
So record explicitly that the caller has given up on the call, and only
park the worker in that case.
Fixes: 4b2c033b5bc9 ("efi/runtime-wrappers: retire the worker if a wedged call ever returns")
Cc: Breno Leitao <leitao@debian.org>
Reviewed-by: Breno Leitao <leitao@debian.org>
Signed-off-by: Ard Biesheuvel <ardb@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/stackcollapse.py')
0 files changed, 0 insertions, 0 deletions
