From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-it0-f72.google.com (mail-it0-f72.google.com [209.85.214.72]) by kanga.kvack.org (Postfix) with ESMTP id 292596B0005 for ; Thu, 28 Jun 2018 14:26:43 -0400 (EDT) Received: by mail-it0-f72.google.com with SMTP id 13-v6so7315674itl.7 for ; Thu, 28 Jun 2018 11:26:43 -0700 (PDT) Received: from mail-sor-f65.google.com (mail-sor-f65.google.com. [209.85.220.65]) by mx.google.com with SMTPS id x73-v6sor2780374iod.259.2018.06.28.11.26.41 for (Google Transport Security); Thu, 28 Jun 2018 11:26:41 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <20180627181138.14c9b66e13b8778506205f89@linux-foundation.org> References: <20180627160800.3dc7f9ee41c0badbf7342520@linux-foundation.org> <20180627181138.14c9b66e13b8778506205f89@linux-foundation.org> From: Andrey Konovalov Date: Thu, 28 Jun 2018 20:26:39 +0200 Message-ID: Subject: Re: [PATCH v4 00/17] khwasan: kernel hardware assisted address sanitizer Content-Type: text/plain; charset="UTF-8" Sender: owner-linux-mm@kvack.org List-ID: To: Andrew Morton Cc: Vishwath Mohan , Kostya Serebryany , Andrey Ryabinin , Alexander Potapenko , Dmitry Vyukov , Catalin Marinas , Will Deacon , Christoph Lameter , Mark Rutland , Nick Desaulniers , Marc Zyngier , Dave Martin , Ard Biesheuvel , "Eric W . Biederman" , Ingo Molnar , Paul Lawrence , Geert Uytterhoeven , Arnd Bergmann , "Kirill A. Shutemov" , Greg Kroah-Hartman , Kate Stewart , Mike Rapoport , kasan-dev , linux-doc@vger.kernel.org, LKML , Linux ARM , linux-sparse@vger.kernel.org, Linux Memory Management List , Linux Kbuild mailing list , Evgenii Stepanov , Lee Smith , Ramana Radhakrishnan , Jacob Bramley , Ruben Ayrapetyan , Jann Horn , Mark Brand , Chintan Pandya On Thu, Jun 28, 2018 at 3:11 AM, Andrew Morton wrote: > On Wed, 27 Jun 2018 17:59:00 -0700 Vishwath Mohan wrote: >> 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 >> >> >> >> 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. I'll add it to the changelog in v5. Thanks!