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:   Fri, 21 Jun 2019 11:43:58 +0200
From:   Arnd Bergmann <>
To:     Kees Cook <>
Cc:     Andrey Ryabinin <>,
        Alexander Potapenko <>,
        Dmitry Vyukov <>,
        kasan-dev <>,
        Alexander Popov <>,
        Ard Biesheuvel <>,
        James Morris <>,
        "Serge E. Hallyn" <>,
        Masahiro Yamada <>,
        LSM List <>,
        Linux Kernel Mailing List <>
Subject: Re: [PATCH] structleak: disable BYREF_ALL in combination with KASAN_STACK

On Thu, Jun 20, 2019 at 7:36 PM Kees Cook <> wrote:
> 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?)

Having it in 5.2 would be great. I had not done much build testing in the last
months, so I didn't actually realize that your patch was merged a while ago
rather than only in linux-next.

BTW, I have now run into a small number of files that are still affected
by a stack overflow warning from STRUCTLEAK_BYREF_ALL. I'm trying
to come up with patches for those as well, we can probably do it in a way
that also improves the affected drivers. I'll put you on Cc when I
find another one.


Powered by blists - more mailing lists