summaryrefslogtreecommitdiff
path: root/scripts/Makefile.thinlto
diff options
context:
space:
mode:
authorSamuel Holland <samuel.holland@sifive.com>2026-08-31 19:11:23 -0600
committerPaul Walmsley <pjw@kernel.org>2026-08-31 19:11:23 -0600
commit2d2184ac90365a4af3274e23c98d469f09f91749 (patch)
treed59f295a3be2c10ea6371a8421ca48ad9d9a3579 /scripts/Makefile.thinlto
parent8718e5a3090bbfd759801d088b700aab21e8e989 (diff)
downloadlinux-stable-2d2184ac90365a4af3274e23c98d469f09f91749.tar.gz
linux-stable-2d2184ac90365a4af3274e23c98d469f09f91749.zip
Revert "riscv: Reset pmm when PR_TAGGED_ADDR_ENABLE is not set"
This reverts commit 3033b2b1e3949274f33a140e2a97571b5a307298. The reverted patch is userspace-visible behavior change, not a bug fix. The two variables here (pmm and pmlen) control two independent features: pmm is the _hardware_ pointer masking mode that applies while executing in userspace. pmlen is the shift amount that the _kernel_ uses when untagging addresses; PMLEN_0 means no untagging occurs, so the kernel does not accept tagged addresses in syscall arguments. It is valid (as documented and tested by the self test) to enable pointer masking without enabling the tagged address ABI. This separation is necessary to allow userspace to create an execution environment similar to what the kernel supports on arm64 by default, where TBI is enabled but the tagged address ABI is not. (On arm64, there is no equivalent to PR_PMLEN_MASK because TBI is always enabled.) Signed-off-by: Samuel Holland <samuel.holland@sifive.com> Link: https://patch.msgid.link/20260820014551.1979772-1-samuel.holland@sifive.com Cc: stable@vger.kernel.org Fixes: 3033b2b1e394 ("riscv: Reset pmm when PR_TAGGED_ADDR_ENABLE is not set") Signed-off-by: Paul Walmsley <pjw@kernel.org>
Diffstat (limited to 'scripts/Makefile.thinlto')
0 files changed, 0 insertions, 0 deletions