On Fri, Sep 25, 2020 at 12:50AM +0200, Andrey Konovalov wrote: > Currently only generic KASAN mode supports vmalloc, reflect that > in the config. > > Signed-off-by: Andrey Konovalov <andreyknvl@xxxxxxxxxx> > Signed-off-by: Vincenzo Frascino <vincenzo.frascino@xxxxxxx> Reviewed-by: Marco Elver <elver@xxxxxxxxxx> > --- > Change-Id: I1889e5b3bed28cc5d607802fb6ae43ba461c0dc1 > --- > lib/Kconfig.kasan | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/lib/Kconfig.kasan b/lib/Kconfig.kasan > index 047b53dbfd58..e1d55331b618 100644 > --- a/lib/Kconfig.kasan > +++ b/lib/Kconfig.kasan > @@ -156,7 +156,7 @@ config KASAN_SW_TAGS_IDENTIFY > > config KASAN_VMALLOC > bool "Back mappings in vmalloc space with real shadow memory" > - depends on HAVE_ARCH_KASAN_VMALLOC > + depends on KASAN_GENERIC && HAVE_ARCH_KASAN_VMALLOC > help > By default, the shadow region for vmalloc space is the read-only > zero page. This means that KASAN cannot detect errors involving > -- > 2.28.0.681.g6f77f65b4e-goog >
