From 253dae48c51ca14de73b66c23c4ad0041879af45 Mon Sep 17 00:00:00 2001 From: Dan Li Date: Wed, 8 Dec 2021 15:56:24 +0800 Subject: [PATCH] arm64: Mark __stack_chk_guard as __ro_after_init stable inclusion from linux-4.19.209 commit 93cb263d81bc9b67abd2e250a3caa21fb983a5e1 -------------------------------- [ Upstream commit 9fcb2e93f41c07a400885325e7dbdfceba6efaec ] __stack_chk_guard is setup once while init stage and never changed after that. Although the modification of this variable at runtime will usually cause the kernel to crash (so does the attacker), it should be marked as __ro_after_init, and it should not affect performance if it is placed in the ro_after_init section. Signed-off-by: Dan Li Acked-by: Mark Rutland Link: https://lore.kernel.org/r/1631612642-102881-1-git-send-email-ashimida@linux.alibaba.com Signed-off-by: Catalin Marinas Signed-off-by: Sasha Levin Acked-by: Jason Yan Signed-off-by: Yang Yingliang --- arch/arm64/kernel/process.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/arm64/kernel/process.c b/arch/arm64/kernel/process.c index 406744566cbe..e5be78915632 100644 --- a/arch/arm64/kernel/process.c +++ b/arch/arm64/kernel/process.c @@ -62,7 +62,7 @@ #ifdef CONFIG_STACKPROTECTOR #include -unsigned long __stack_chk_guard __read_mostly; +unsigned long __stack_chk_guard __ro_after_init; EXPORT_SYMBOL(__stack_chk_guard); #endif -- GitLab