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:   Fri, 3 Mar 2017 15:51:41 +0100
From:   Arnd Bergmann <>
To:     Alexander Potapenko <>
Cc:     Andrey Ryabinin <>,
        kasan-dev <>,
        Dmitry Vyukov <>,
        Networking <>,
        LKML <>,,
        linux-wireless <>,,
        "David S . Miller" <>
Subject: Re: [PATCH 01/26] compiler: introduce noinline_for_kasan annotation

On Fri, Mar 3, 2017 at 3:33 PM, Alexander Potapenko <> wrote:
> On Fri, Mar 3, 2017 at 3:30 PM, Arnd Bergmann <> wrote:
>> On Fri, Mar 3, 2017 at 2:55 PM, Alexander Potapenko <> wrote:
>> Would KMSAN also force local variables to be non-overlapping the way that
>> asan-stack=1 and -fsanitize-address-use-after-scope do? As I understood it,
>> KMSAN would add extra code for maintaining the uninit bits, but in an example
>> like this
> The thing is that KMSAN (and other tools that insert heavyweight
> instrumentation) may cause heavy register spilling which will also
> blow up the stack frames.

In that case, I would expect a mostly distinct set of functions to have large
stack frames with KMSAN, compared to the ones that need
noinline_for_kasan. In most cases I patched, the called inline function is
actually trivial, but invoked many times from the same caller.


Powered by blists - more mailing lists