From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrey Konovalov Subject: Re: [PATCH v6 00/18] khwasan: kernel hardware assisted address sanitizer Date: Thu, 6 Sep 2018 13:06:23 +0200 Message-ID: References: <20180905141032.b1ddaab53d1b2b3bada95415@linux-foundation.org> <20180906100543.GI3592@arm.com> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Return-path: In-Reply-To: <20180906100543.GI3592@arm.com> Sender: linux-kernel-owner@vger.kernel.org To: Will Deacon Cc: Andrew Morton , Andrey Ryabinin , Alexander Potapenko , Dmitry Vyukov , Catalin Marinas , 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 List-Id: linux-sparse@vger.kernel.org On Thu, Sep 6, 2018 at 12:05 PM, Will Deacon wrote: > On Wed, Sep 05, 2018 at 02:10:32PM -0700, Andrew Morton wrote: >> On Wed, 29 Aug 2018 13:35:04 +0200 Andrey Konovalov wrote: >> >> > This patchset adds a new mode to KASAN [1], which is called KHWASAN >> > (Kernel HardWare assisted Address SANitizer). >> >> We're at v6 and there are no reviewed-by's or acked-by's to be seen. >> Is that a fair commentary on what has been happening, or have people >> been remiss in sending and gathering such things? > > I still have concerns about the consequences of merging this as anything > other than a debug option [1]. Unfortunately, merging it as a debug option > defeats the whole point, so I think we need to spend more effort on developing > tools that can help us to find and fix the subtle bugs which will arise from > enabling tagged pointers in the kernel. I totally don't mind calling it a debug option. Do I need to somehow specify it somewhere? Why does it defeat the point? The point is to ease KASAN-like testing on devices with limited memory.