linux-kernel - Re: [PATCH v4 00/17] khwasan: kernel hardware assisted address sanitizer

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

Date:   Wed, 27 Jun 2018 18:11:38 -0700
From:   Andrew Morton <akpm@...ux-foundation.org>
To:     Vishwath Mohan <vishwath@...gle.com>
Cc:     Kostya Serebryany <kcc@...gle.com>, andreyknvl@...gle.com,
        aryabinin@...tuozzo.com, Alexander Potapenko <glider@...gle.com>,
        Dmitry Vyukov <dvyukov@...gle.com>, catalin.marinas@....com,
        will.deacon@....com, cl@...ux.com, mark.rutland@....com,
        Nick Desaulniers <ndesaulniers@...gle.com>,
        marc.zyngier@....com, dave.martin@....com,
        ard.biesheuvel@...aro.org, ebiederm@...ssion.com, mingo@...nel.org,
        Paul Lawrence <paullawrence@...gle.com>, geert@...ux-m68k.org,
        arnd@...db.de, kirill.shutemov@...ux.intel.com,
        gregkh@...uxfoundation.org, kstewart@...uxfoundation.org,
        rppt@...ux.vnet.ibm.com, kasan-dev@...glegroups.com,
        linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
        linux-arm-kernel@...ts.infradead.org, linux-sparse@...r.kernel.org,
        linux-mm@...ck.org, linux-kbuild@...r.kernel.org,
        Evgenii Stepanov <eugenis@...gle.com>, Lee.Smith@....com,
        Ramana.Radhakrishnan@....com, Jacob.Bramley@....com,
        Ruben.Ayrapetyan@....com, Jann Horn <jannh@...gle.com>,
        Mark Brand <markbrand@...gle.com>, cpandya@...eaurora.org
Subject: Re: [PATCH v4 00/17] khwasan: kernel hardware assisted address
 sanitizer

On Wed, 27 Jun 2018 17:59:00 -0700 Vishwath Mohan <vishwath@...gle.com> wrote:

> > > > time consume much less memory, trading that off for somewhat imprecise
> > > > bug detection and being supported only for arm64.
> > >
> > > Why do we consider this to be a worthwhile change?
> > >
> > > Is KASAN's memory consumption actually a significant problem?  Some
> > > data regarding that would be very useful.
> >
> > On mobile, ASAN's and KASAN's memory usage is a significant problem.
> > Not sure if I can find scientific evidence of that.
> > CC-ing Vishwath Mohan who deals with KASAN on Android to provide
> > anecdotal evidence.
> >
> Yeah, I can confirm that it's an issue. Like Kostya mentioned, I don't have
> data on-hand, but anecdotally both ASAN and KASAN have proven problematic
> to enable for environments that don't tolerate the increased memory
> pressure well. This includes,
> (a) Low-memory form factors - Wear, TV, Things, lower-tier phones like Go
> (c) Connected components like Pixel's visual core
> <https://www.blog.google/products/pixel/pixel-visual-core-image-processing-and-machine-learning-pixel-2/>
> 
> 
> These are both places I'd love to have a low(er) memory footprint option at
> my disposal.

Thanks.

It really is important that such information be captured in the
changelogs.  In as much detail as can be mustered.