diff options
| author | GONG, Ruiqi <gongruiqi1@huawei.com> | 2022-06-29 14:04:23 +0800 |
|---|---|---|
| committer | Kees Cook <keescook@chromium.org> | 2022-07-01 18:01:47 -0700 |
| commit | 375561bd6195a31bf4c109732bd538cb97a941f4 (patch) | |
| tree | 21dd1b31b60ca9202e8f9af370d91e0c4e4e8f49 /init | |
| parent | 6a022dd29f2cefbac4895a34e2e1f14b2d12d819 (diff) | |
| download | linux-375561bd6195a31bf4c109732bd538cb97a941f4.tar.gz linux-375561bd6195a31bf4c109732bd538cb97a941f4.tar.bz2 linux-375561bd6195a31bf4c109732bd538cb97a941f4.zip | |
stack: Declare {randomize_,}kstack_offset to fix Sparse warnings
Fix the following Sparse warnings that got noticed when the PPC-dev
patchwork was checking another patch (see the link below):
init/main.c:862:1: warning: symbol 'randomize_kstack_offset' was not declared. Should it be static?
init/main.c:864:1: warning: symbol 'kstack_offset' was not declared. Should it be static?
Which in fact are triggered on all architectures that have
HAVE_ARCH_RANDOMIZE_KSTACK_OFFSET support (for instances x86, arm64
etc).
Link: https://lore.kernel.org/lkml/e7b0d68b-914d-7283-827c-101988923929@huawei.com/T/#m49b2d4490121445ce4bf7653500aba59eefcb67f
Cc: Christophe Leroy <christophe.leroy@csgroup.eu>
Cc: Xiu Jianfeng <xiujianfeng@huawei.com>
Signed-off-by: GONG, Ruiqi <gongruiqi1@huawei.com>
Reviewed-by: Christophe Leroy <christophe.leroy@csgroup.eu>
Fixes: 39218ff4c625 ("stack: Optionally randomize kernel stack offset each syscall")
Signed-off-by: Kees Cook <keescook@chromium.org>
Link: https://lore.kernel.org/r/20220629060423.2515693-1-gongruiqi1@huawei.com
Diffstat (limited to 'init')
| -rw-r--r-- | init/main.c | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/init/main.c b/init/main.c index 0ee39cdcfcac..91642a4e69be 100644 --- a/init/main.c +++ b/init/main.c @@ -99,6 +99,7 @@ #include <linux/kcsan.h> #include <linux/init_syscalls.h> #include <linux/stackdepot.h> +#include <linux/randomize_kstack.h> #include <net/net_namespace.h> #include <asm/io.h> |