linux-kernel - Re: [GIT PULL] meminit fix for v5.3-rc2

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] [thread-next>] [day] [month] [year] [list]

Date:   Sun, 28 Jul 2019 12:43:15 -0700
From:   Linus Torvalds <torvalds@...ux-foundation.org>
To:     Kees Cook <keescook@...omium.org>
Cc:     Linux List Kernel Mailing <linux-kernel@...r.kernel.org>,
        Arnd Bergmann <arnd@...db.de>
Subject: Re: [GIT PULL] meminit fix for v5.3-rc2

On Sun, Jul 28, 2019 at 12:21 PM Kees Cook <keescook@...omium.org> wrote:
>
> Please pull this meminit fix for v5.3-rc2.

Side noe: I find "meminit" a confusing description for the structleak
thing. When I hear it, it sounds like some generic memory
initialization thing in the VM layer (which we obviously do also
have), not the stack variable initialization.

Also, have you guys talked to gcc people about just making it a real
feature, like I think it is for clang? In particular, I still suspect
that we could/should  just make zero-filling the *default* in the long
run, and say "our C standard is that local variables are initialized
to zero, exactly the same way static variables are".

I know you posted some numbers somewhere (well, I'm pretty sure you
did) and the full stack initialization really was pretty cheap,
wasn't it?

               Linus