linux-kernel - Re: [PATCH 4/4] context_tracking: uninitialize static variables

lists.openwall.net		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 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Mon, 3 Aug 2020 11:27:54 +0100 (BST)
From:   Jules Irenge <jbi.octave@...il.com>
To:     peterz@...radead.org
cc:     Jules Irenge <jbi.octave@...il.com>, linux-kernel@...r.kernel.org,
        Frederic Weisbecker <frederic@...nel.org>,
        Thomas Gleixner <tglx@...utronix.de>,
        Alexandre Chartre <alexandre.chartre@...cle.com>,
        Masami Hiramatsu <mhiramat@...nel.org>
Subject: Re: [PATCH 4/4] context_tracking: uninitialize static variables



On Mon, 3 Aug 2020, peterz@...radead.org wrote:
 
> So personally I prefer having the '= false' there. It used to be that
> compilers were stupid and would put any initialized static variable in
> .data, even if it was initialized with 0. But AFAIK compilers are no
> longer that stupid.
> 
Thanks for the reply, I completely understand the precaution measure.