Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
MIME-Version: 1.0
References: <201907281218.F6D2C2DD@keescook> <CAHk-=wj+1vDh2=eZExibYF9Lo0GsGxaAjxCSwpUFVURrN44cUQ@mail.gmail.com>
In-Reply-To: <CAHk-=wj+1vDh2=eZExibYF9Lo0GsGxaAjxCSwpUFVURrN44cUQ@mail.gmail.com>
From:   Linus Torvalds <torvalds@linux-foundation.org>
Date:   Sun, 28 Jul 2019 12:50:18 -0700
Message-ID: <CAHk-=whUmaEX0HATrs1Nsde3Nz+MXn=Tg1_9jL8u2Rd5Wz=oCg@mail.gmail.com>
Subject: Re: [GIT PULL] meminit fix for v5.3-rc2
To:     Kees Cook <keescook@chromium.org>
Cc:     Linux List Kernel Mailing <linux-kernel@vger.kernel.org>,
        Arnd Bergmann <arnd@arndb.de>
Content-Type: text/plain; charset="UTF-8"
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On Sun, Jul 28, 2019 at 12:43 PM Linus Torvalds
<torvalds@linux-foundation.org> wrote:
>
> Side note: I find "meminit" a confusing description for the structleak
> thing.

Not that 'structleak' is all that much better, because it's not
necessarily just about structs either.

'stack variable initialization' is too long. I dunno. But it's more
about "variables" (and in the case of kmalloc etc - perhaps
'allocations') than "memory", I feel.

The point is that in the kernel we do memory management and memory
initialization, and that's something very different.

                     Linus