[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Wed, 11 Nov 2020 19:53:14 +0100
From: Andrey Konovalov <andreyknvl@...gle.com>
To: Alexander Potapenko <glider@...gle.com>
Cc: Catalin Marinas <catalin.marinas@....com>,
Will Deacon <will.deacon@....com>,
Vincenzo Frascino <vincenzo.frascino@....com>,
Dmitry Vyukov <dvyukov@...gle.com>,
Andrey Ryabinin <aryabinin@...tuozzo.com>,
Marco Elver <elver@...gle.com>,
Evgenii Stepanov <eugenis@...gle.com>,
Branislav Rankov <Branislav.Rankov@....com>,
Kevin Brodsky <kevin.brodsky@....com>,
Andrew Morton <akpm@...ux-foundation.org>,
kasan-dev <kasan-dev@...glegroups.com>,
Linux ARM <linux-arm-kernel@...ts.infradead.org>,
Linux Memory Management List <linux-mm@...ck.org>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v9 25/44] kasan: introduce CONFIG_KASAN_HW_TAGS
On Wed, Nov 11, 2020 at 4:58 PM Alexander Potapenko <glider@...gle.com> wrote:
>
> On Tue, Nov 10, 2020 at 11:12 PM Andrey Konovalov <andreyknvl@...gle.com> wrote:
> >
> > This patch adds a configuration option for a new KASAN mode called
> > hardware tag-based KASAN. This mode uses the memory tagging approach
> > like the software tag-based mode, but relies on arm64 Memory Tagging
> > Extension feature for tag management and access checking.
> >
> > Signed-off-by: Andrey Konovalov <andreyknvl@...gle.com>
> > Co-developed-by: Vincenzo Frascino <vincenzo.frascino@....com>
> > Signed-off-by: Vincenzo Frascino <vincenzo.frascino@....com>
> > Reviewed-by: Marco Elver <elver@...gle.com>
> > ---
> > Change-Id: I246c2def9fffa6563278db1bddfbe742ca7bdefe
> > ---
> > lib/Kconfig.kasan | 58 +++++++++++++++++++++++++++++++++--------------
> > 1 file changed, 41 insertions(+), 17 deletions(-)
> >
> > diff --git a/lib/Kconfig.kasan b/lib/Kconfig.kasan
> > index ec59a0e26d09..e5f27ec8b254 100644
> > --- a/lib/Kconfig.kasan
> > +++ b/lib/Kconfig.kasan
> > @@ -6,7 +6,10 @@ config HAVE_ARCH_KASAN
> > config HAVE_ARCH_KASAN_SW_TAGS
> > bool
> >
> > -config HAVE_ARCH_KASAN_VMALLOC
> > +config HAVE_ARCH_KASAN_HW_TAGS
> > + bool
> > +
> > +config HAVE_ARCH_KASAN_VMALLOC
> > bool
> >
> > config CC_HAS_KASAN_GENERIC
> > @@ -20,11 +23,11 @@ config CC_HAS_WORKING_NOSANITIZE_ADDRESS
> It might make sense to add a comment to
> CC_HAS_WORKING_NOSANITIZE_ADDRESS describing which modes need it (and
> why).
OK, will do in v10, thanks!
Powered by blists - more mailing lists