summaryrefslogtreecommitdiff
path: root/arch
diff options
context:
space:
mode:
authorMark Brown <broonie@kernel.org>2025-11-29 00:48:45 +0000
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2026-01-02 12:57:23 +0100
commit5bb88024409ef7bb53e5d42d35097a7a3157f764 (patch)
tree2eb98ba297d377a2f90c62a2914ca7ba62ad20a6 /arch
parent7992a8c946890a1a6d870bfac4e737a71a8a1676 (diff)
downloadlinux-5bb88024409ef7bb53e5d42d35097a7a3157f764.tar.gz
linux-5bb88024409ef7bb53e5d42d35097a7a3157f764.tar.bz2
linux-5bb88024409ef7bb53e5d42d35097a7a3157f764.zip
arm64/gcs: Flush the GCS locking state on exec
commit 98a97bf41528ef738b06eb07ec2b2eb1cfde6ce6 upstream. When we exec a new task we forget to flush the set of locked GCS mode bits. Since we do flush the rest of the state this means that if GCS is locked the new task will be unable to enable GCS, it will be locked as being disabled. Add the expected flush. Fixes: fc84bc5378a8 ("arm64/gcs: Context switch GCS state for EL0") Cc: <stable@vger.kernel.org> # 6.13.x Reported-by: Yury Khrustalev <Yury.Khrustalev@arm.com> Signed-off-by: Mark Brown <broonie@kernel.org> Tested-by: Yury Khrustalev <yury.khrustalev@arm.com> Signed-off-by: Catalin Marinas <catalin.marinas@arm.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'arch')
-rw-r--r--arch/arm64/kernel/process.c1
1 files changed, 1 insertions, 0 deletions
diff --git a/arch/arm64/kernel/process.c b/arch/arm64/kernel/process.c
index fba7ca102a8c..489554931231 100644
--- a/arch/arm64/kernel/process.c
+++ b/arch/arm64/kernel/process.c
@@ -292,6 +292,7 @@ static void flush_gcs(void)
current->thread.gcs_base = 0;
current->thread.gcs_size = 0;
current->thread.gcs_el0_mode = 0;
+ current->thread.gcs_el0_locked = 0;
write_sysreg_s(GCSCRE0_EL1_nTR, SYS_GCSCRE0_EL1);
write_sysreg_s(0, SYS_GCSPR_EL0);
}