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:   Thu, 20 Jun 2019 10:35:56 -0700
From:   Kees Cook <>
To:     Arnd Bergmann <>
Cc:     Andrey Ryabinin <>,
        Alexander Potapenko <>,
        Dmitry Vyukov <>,,
        Alexander Popov <>,
        Ard Biesheuvel <>,
        James Morris <>,
        "Serge E. Hallyn" <>,
        Masahiro Yamada <>,,
Subject: Re: [PATCH] structleak: disable BYREF_ALL in combination with

On Tue, Jun 18, 2019 at 11:47:13AM +0200, Arnd Bergmann wrote:
> leads to much larger kernel stack usage, as seen from the warnings
> about functions that now exceed the 2048 byte limit:

Is the preference that this go into v5.2 (there's not much time left),
or should this be v5.3? (You didn't mark it as Cc: stable?)

> one. I picked the dependency in GCC_PLUGIN_STRUCTLEAK_BYREF_ALL, as
> this option is designed to make uninitialized stack usage less harmful
> when enabled on its own, but it also prevents KASAN from detecting those
> cases in which it was in fact needed.

Right -- there's not much sense in both being enabled. I'd agree with
this rationale.

Kees Cook

Powered by blists - more mailing lists