lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Sat,  1 Aug 2020 19:46:03 +0100
From:   Jules Irenge <>
Cc:     Jules Irenge <>,
        Peter Zijlstra <>,
        Frederic Weisbecker <>,
        Thomas Gleixner <>,
        Alexandre Chartre <>,
        Masami Hiramatsu <>
Subject: [PATCH 4/4] context_tracking: uninitialize static variables

Checkpatch tool reports an error at a staic variable declaration

"ERROR: do not initialise statics to false"

This is due to the fact that this variable is stored in the buffer
In the .bss section, one can not set an initial value
Here we can trust the compiler to automatically set them to false.
The variable has since been uninitialized.

Signed-off-by: Jules Irenge <>
 kernel/context_tracking.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/kernel/context_tracking.c b/kernel/context_tracking.c
index 36a98c48aedc..21881c534152 100644
--- a/kernel/context_tracking.c
+++ b/kernel/context_tracking.c
@@ -190,7 +190,7 @@ NOKPROBE_SYMBOL(context_tracking_user_exit);
 void __init context_tracking_cpu_set(int cpu)
-	static __initdata bool initialized = false;
+	static __initdata bool initialized;
 	if (!per_cpu(, cpu)) {
 		per_cpu(, cpu) = true;

Powered by blists - more mailing lists