From: Dan Li Date: Tue, 14 Sep 2021 09:44:02 +0000 (+0800) Subject: arm64: Mark __stack_chk_guard as __ro_after_init X-Git-Tag: baikal/aarch64/sdk6.1~5736^2 X-Git-Url: https://git.baikalelectronics.ru/sdk/?a=commitdiff_plain;h=11c5abb05c32bb6f14ac9c27971e44fd6943838d;p=kernel.git arm64: Mark __stack_chk_guard as __ro_after_init __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 --- diff --git a/arch/arm64/kernel/process.c b/arch/arm64/kernel/process.c index 1a1213cca1731..40adb8cdbf5af 100644 --- a/arch/arm64/kernel/process.c +++ b/arch/arm64/kernel/process.c @@ -57,7 +57,7 @@ #if defined(CONFIG_STACKPROTECTOR) && !defined(CONFIG_STACKPROTECTOR_PER_TASK) #include -unsigned long __stack_chk_guard __read_mostly; +unsigned long __stack_chk_guard __ro_after_init; EXPORT_SYMBOL(__stack_chk_guard); #endif