From mboxrd@z Thu Jan 1 00:00:00 1970 Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.remote-ip=100.103.45.18 ARC-Seal: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; cv=none; t=1793815794; b=zfnQuJbGfstQsAhgu9ti27ZzP7EQaQbpfpi9idN3c+qu70Rq0PPVoJl1veKPCNri26lv UfGcTNBJTiLg30owe28DS5+cYQYPOqvf9zjj1FSKZDoLyP1aTPeTXlK5c4eZQSuD80sOY ydYynb6G8A7Tw2+NhcqFP8KWMUSVmRvs8g/0/jRvQ20XvkPM9g70Nw4GBSK4OLJ7bEWgN yLjG8Agr556w2gDkcNqZJguzT+ZU9pT3U7wAhWQhi1Uk94oLaEgMKicyiNnzRI/tNDgFZ UUQStLkve8jfFw+KGhKaJtKdYwsz1FP3ncXhE6UOkaEHcabxnd/YGnoTFZpmje0vYMQ== ARC-Message-Signature: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; c=relaxed/relaxed; t=1793815794; h=Received:DKIM-Signature:Received:Received:X-ME-Sender:X-ME-Received: X-ME-Proxy-Cause:X-ME-Proxy:Feedback-ID:Received:From:To:Cc:Subject: Date:Message-ID:X-Mailer:In-Reply-To:References:MIME-Version: Content-Transfer-Encoding; bh=xYhA+4xs8LRrA1wJe9S44qbgci30j0A5eEtwpktcSPc=; b=AH+3refmsPlu6YOuE2vNQAcKm7duLW4YZRP4h0t5v9+8rMmiuuudfbXvW25SFjBo31OU eg+CnfxXQ+sgL4SrcYFppeTxQev6dUVvOZ1iF6AeHVa8OTvV7iO8WhXBc7x27aamzzTQE QPpxOL0z5ozAf7GmBC8iIwdKewNat+bBHv937iHGVdBI27CRaylKmyjt+tFK6xpZsuYnX OFfnhxFQDZrZXoL5NSKB9+IkgCgIOd5l8uk3ZV44Qcs2FLoS2AuBOP48uRgmpMEmCKvxb oR5UXn0BAV1nBjCPRRAEdCzvmup4p/TjKBQhGuN3RNrK15dvzntQjn00WbKlvW3KYdg== ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dkim=pass header.d=kernel.org header.i=@kernel.org header.a=rsa-sha256 header.s=k20260515 header.b=oBTFMgW6; arc=none smtp.remote-ip=100.103.45.18 Received: from smtp.kernel.org (quasi.space.kernel.org [100.103.45.18]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (prime256v1)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 154B7606BDF4; Wed, 4 Nov 2026 18:09:54 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key, unprotected) header.d=kernel.org header.i=@kernel.org header.a=rsa-sha256 header.s=k20260515 header.b=oBTFMgW6 Received: by smtp.kernel.org (Postfix) with ESMTPSA id C4F691F00A17; Wed, 4 Nov 2026 18:09:52 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org; s=k20260515; t=1793815793; bh=xYhA+4xs8LRrA1wJe9S44qbgci30j0A5eEtwpktcSPc=; h=From:To:Cc:Subject:Date:In-Reply-To:References; b=oBTFMgW62r5H7V8sS25AUwVRE4dHUlCHbLianBddK8QCXaMNSR7HTCuk3K1KIYnm8 YH26cQ3rnhIp0RETUNghG8Nk4CZ0KXHTUBZRi0phWWqcjRWAn60+WFnr1I1R4T1/8e zVaxVJDVdWMmhmMTrXh7jJJgOZj9mshXnSU8LeOCWjIADiXEu5eZgddXwRfw4iHzRB 1uQ57qLQniYlm+IKqtBHj2UCUszD8k3pDBJlptwugCWkYuGHPaEWuH8yf4ASnJplnG 8DC92oEE/eJeHy7niXTNqSgTLxgysGZ053dZ57UFzJF+2Fqfm5nzRz/+tI8RyXVm4l C9VlibnGe1uWQ== Received: from phl-compute-12.internal (phl-compute-12.internal [10.202.2.52]) by mailfauth.ams.internal (Postfix) with ESMTP id 24C2C1980047; Wed, 4 Nov 2026 13:09:50 -0500 (EST) Received: from phl-frontend-03 ([10.202.2.162]) by phl-compute-12.internal (MEProxy); Wed, 04 Nov 2026 13:09:51 -0500 X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: dmFkZTEUECgwQL3C5tdkKY31fLAMH2TFPvlSFTmgoaQDjvGEstJkEbBuZhfW1c+T6XD2n+ lW7bAtMeDt5da3vYSJBwd0X66UVSR7ch1n2g1lGpR0+xt0GpSQ7KAvlNKq5bl/O67KSF19 HoiGuJKgrLbOr6wuxPPpDHzqOXbbSi2nDXwYdBnBynrAwMGXdCJ45MdnKqlmOm217SU07Z qCgmEhe6yRm/Dm+3upbU3Sx75TXlkGmrCgs9JDgItJZSc4mT3nNQUrhu67R8Yq/3eOlwag A/VaZl3IdrUgSgHNALxCDSb9KTbh4KVBahW7mmzVzC3kGcV5vpsReEU8nSqDOkRjRxXDkT 29ghDJOB25oG2CHNpk8Xt7P0RvZvBUutX/Qxd/BqyiHZeNkHpLuFs5yrQzxFfhywy1ZbS9 zdpBQ0aQqtVfdQbe98GJ1Z2SHx1H6GhD3WDxslll3xCHeNgWNGOkhATq/iyWAaDRa+7ZB8 EtM1zsSZxwtqYxgIdiBhg0ag2Xp6O1nyUoAKBSjeSw2j+yp9KW+vIgJwtEfhJwYi6ejes2 qyPEioxngkdRBVzUDJ9bLRswioJe7gleg7VQ4ERc8e3pIHnYk5rSNyxLa5QNIV8XnFqWRV GkQ1LkyqY4utAzEuhFFw8hZ2d9JQE2Y3Pmdx/gUAg4Swj3UU8aBUD9YgDnaw X-ME-Proxy: Feedback-ID: i10464835:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 4 Nov 2026 13:09:49 -0500 (EST) From: "Kiryl Shutsemau (Meta)" To: Catalin Marinas , Will Deacon , Mark Rutland , James Morse Cc: "Kiryl Shutsemau (Meta)" , Marc Zyngier , Doug Anderson , Usama Arif , Breno Leitao , Dawei Li , mrigendrachaubey , kernel-team@meta.com, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, stable@vger.kernel.org Subject: [PATCH 2/2] arm64: sdei: Preserve the interrupted context's exception registers Date: Wed, 4 Nov 2026 18:09:34 +0000 Message-ID: <20261104180936.2981070-3-kas@kernel.org> X-Mailer: git-send-email 2.54.0 In-Reply-To: <20261104180936.2981070-1-kas@kernel.org> References: <20261104180936.2981070-1-kas@kernel.org> X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Post: List-Help: List-Subscribe: List-Unsubscribe: List-Owner: Precedence: list MIME-Version: 1.0 Content-Transfer-Encoding: 8bit An SDEI event is dispatched by firmware regardless of PSTATE.DAIF, so it can interrupt the kernel where the exception registers are live: - exception entry, before kernel_entry has saved ELR_EL1/SPSR_EL1 and before the C handler has read ESR_EL1/FAR_EL1; - exception return, after kernel_exit has loaded ELR_EL1/SPSR_EL1 and before the ERET. An IRQ or pseudo-NMI cannot arrive there with PSTATE.I set. Firmware saves only x0-x17, PC and PSTATE around an SDEI event, so a synchronous exception taken by the handler overwrites the interrupted context's ELR, SPSR, ESR and FAR. do_sdei_event() only notices that ELR changed, and warns. The interrupted context then carries on with the handler's state. A task interrupted on its way into the kernel can be sent SIGILL for the handler's kernel data abort. A task interrupted on its way back to user space ERETs to EL1, at the handler's fixup address, with user registers loaded. With SDEI delivering NMI backtraces, this happens in normal operation. The handler runs show_regs(), which reads through possibly-NULL pointers with the _nofault() accessors. print_worker_info() faults this way for a kworker that is not running a work item, and a single sysrq-l warned once per such kworker. Save ELR, SPSR, ESR and FAR on entry to do_sdei_event() and restore them before returning to firmware. Once they are restored, a nested exception is harmless if its handler is safe in NMI context. That holds for EL1 data aborts on translation, permission and access-flag faults, which never take the mmap lock in NMI context, and for BRK. Warn once, with the syndrome, about any other exception class. Fixes: f5df26961853 ("arm64: kernel: Add arch-specific SDEI entry code and CPU masking") Cc: stable@vger.kernel.org Signed-off-by: Kiryl Shutsemau (Meta) --- arch/arm64/kernel/sdei.c | 61 +++++++++++++++++++++++++++++++++++----- 1 file changed, 54 insertions(+), 7 deletions(-) diff --git a/arch/arm64/kernel/sdei.c b/arch/arm64/kernel/sdei.c index 9fa2a3aeed48..1ea566f30586 100644 --- a/arch/arm64/kernel/sdei.c +++ b/arch/arm64/kernel/sdei.c @@ -196,6 +196,31 @@ unsigned long sdei_arch_get_entry_point(int conduit) return 0; } +/* + * Exceptions an SDEI handler may take without harm once do_sdei_event() has + * restored the interrupted context's exception registers. Their handlers are + * safe in NMI context: + * - EL1 data aborts on translation, permission and access-flag faults: + * faulthandler_disabled() is true in NMI context, so do_page_fault() never + * takes the mmap lock. This covers the _nofault() accessors used by the + * generic dump_stack()/show_regs() code (e.g. print_worker_info()). + * - BRK: kprobes, WARN/BUG, kCFI and UBSAN traps, all NMI-capable. + * Anything else taken at EL1 is fatal on its own, or unexpected here. + */ +static bool sdei_nested_exception_ok(unsigned long esr) +{ + switch (ESR_ELx_EC(esr)) { + case ESR_ELx_EC_DABT_CUR: + return esr_fsc_is_translation_fault(esr) || + esr_fsc_is_permission_fault(esr) || + esr_fsc_is_access_flag_fault(esr); + case ESR_ELx_EC_BRK64: + return true; + default: + return false; + } +} + /* * do_sdei_event() returns one of: * SDEI_EV_HANDLED - success, return to the interrupted context. @@ -209,6 +234,10 @@ unsigned long __kprobes do_sdei_event(struct pt_regs *regs, int i, err = 0; int clobbered_registers = 4; u64 elr = read_sysreg(elr_el1); + u64 spsr = read_sysreg(spsr_el1); + u64 esr = read_sysreg(esr_el1); + u64 far = read_sysreg(far_el1); + u64 nested_elr, nested_esr, nested_far; u32 kernel_mode = read_sysreg(CurrentEL) | 1; /* +SPSel */ unsigned long vbar = read_sysreg(vbar_el1); @@ -237,15 +266,33 @@ unsigned long __kprobes do_sdei_event(struct pt_regs *regs, err = sdei_event_handler(regs, arg); - if (elr != read_sysreg(elr_el1)) { - /* - * We took a synchronous exception from the SDEI handler. - * This could deadlock, and if you interrupt KVM it will - * hyp-panic instead. - */ - pr_warn("unsafe: exception during handler\n"); + /* + * SDEI is not an architectural exception: nothing saved the + * interrupted context's exception registers on the way in, and it may + * be in the middle of exception entry or return (SDEI ignores DAIF). + * Any synchronous exception the handler took has overwritten them. + * Only the last one's syndrome survives; report it if it is not one + * known to be harmless. + * + * If the event interrupted a KVM world switch, VBAR points at the KVM + * hyp vectors and any such exception is a hyp panic instead. + */ + nested_elr = read_sysreg(elr_el1); + nested_esr = read_sysreg(esr_el1); + nested_far = read_sysreg(far_el1); + if (nested_elr != elr && !sdei_nested_exception_ok(nested_esr)) { + pr_warn_once("unexpected exception during handler: ESR %#llx FAR %#llx near %pS\n", + nested_esr, nested_far, (void *)nested_elr); } + /* + * Put them back unconditionally. An unchanged ELR does not rule out a + * nested exception: one may have returned to the same address. + */ + write_sysreg(elr, elr_el1); + write_sysreg(spsr, spsr_el1); + write_sysreg(esr, esr_el1); + write_sysreg(far, far_el1); write_sysreg(vbar, vbar_el1); if (err) -- 2.54.0