Re: [PATCH RFC 07/10] kfence, kmemleak: make KFENCE compatible with KMEMLEAK

2020-09-08 Thread Alexander Potapenko
> Could you instead do: > > #if defined(CONFIG_KFENCE) && defined(CONFIG_HAVE_ARCH_KFENCE_STATIC_POOL) > delete_object_part((unsigned long)__kfence_pool, KFENCE_POOL_SIZE); > #endif Thanks, we'll apply this to v2! -- Alexander Potapenko Software Engineer Google Germany GmbH

Re: [PATCH RFC 07/10] kfence, kmemleak: make KFENCE compatible with KMEMLEAK

2020-09-08 Thread Catalin Marinas
On Mon, Sep 07, 2020 at 03:40:52PM +0200, Marco Elver wrote: > From: Alexander Potapenko > > Add compatibility with KMEMLEAK, by making KMEMLEAK aware of the KFENCE > memory pool. This allows building debug kernels with both enabled, which > also helped in debugging KFENCE. > > Co-developed-by:

[PATCH RFC 07/10] kfence, kmemleak: make KFENCE compatible with KMEMLEAK

2020-09-07 Thread Marco Elver
From: Alexander Potapenko Add compatibility with KMEMLEAK, by making KMEMLEAK aware of the KFENCE memory pool. This allows building debug kernels with both enabled, which also helped in debugging KFENCE. Co-developed-by: Marco Elver Signed-off-by: Marco Elver Signed-off-by: Alexander