diff options
| author | Samuel Holland <samuel.holland@sifive.com> | 2026-08-20 17:56:57 -0600 |
|---|---|---|
| committer | Paul Walmsley <pjw@kernel.org> | 2026-08-20 17:56:57 -0600 |
| commit | e2715cca37c2e20e8428f00fbf14345c2a64f161 (patch) | |
| tree | 185b1317bbcf5d40c81990a953f352d9ee4a863a /scripts | |
| parent | 3c98c447483851b2182b34ab5cb0a12c960a9779 (diff) | |
| download | linux-next-e2715cca37c2e20e8428f00fbf14345c2a64f161.tar.gz linux-next-e2715cca37c2e20e8428f00fbf14345c2a64f161.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')
0 files changed, 0 insertions, 0 deletions