From: Will Deacon <will@kernel.org>
To: linux-arm-kernel@lists.infradead.org, Will Deacon <will@kernel.org>
Cc: catalin.marinas@arm.com, kernel-team@android.com,
linux-kernel@vger.kernel.org, Ard Biesheuvel <ardb@kernel.org>,
Gus Bourg <gus@bourg.net>
Subject: Re: [PATCH] arm64/efi: Avoid voluntary preemption with efi_mm installed
Date: Wed, 12 Aug 2026 13:09:01 +0100 [thread overview]
Message-ID: <178653008050.3619485.9655082628156363695.b4-ty@kernel.org> (raw)
In-Reply-To: <20260811140430.22832-1-will@kernel.org>
On Tue, 11 Aug 2026 15:04:29 +0100, Will Deacon wrote:
> Gus reports a bad kernel memory access when using software PAN
> (CONFIG_ARM64_SW_TTBR0_PAN=y) on a machine with support for EFI runtime
> services:
>
> Unable to handle kernel access to user memory outside uaccess routines
> at virtual address 00000000f322ff30
> Mem abort info:
> ESR = 0x0000000096000004
> FSC = 0x04: level 0 translation fault
> Internal error: Oops: 0000000096000004 [#1] SMP
> Workqueue: efi_rts_wq efi_call_rts
> pstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
> pc : efi_call_rts+0xd8/0x288
> Call trace:
> efi_call_rts+0xd8/0x288 (P)
> process_one_work+0x178/0x4f8
> worker_thread+0x194/0x328
>
> [...]
Applied to arm64 (for-next/mm), thanks!
[1/1] arm64/efi: Avoid voluntary preemption with efi_mm installed
https://git.kernel.org/arm64/c/e98a9d014637
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
prev parent reply other threads:[~2026-08-12 12:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-11 14:04 [PATCH] arm64/efi: Avoid voluntary preemption with efi_mm installed Will Deacon
2026-08-11 14:19 ` Ard Biesheuvel
2026-08-12 12:09 ` Will Deacon [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=178653008050.3619485.9655082628156363695.b4-ty@kernel.org \
--to=will@kernel.org \
--cc=ardb@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=gus@bourg.net \
--cc=kernel-team@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox