kasan: solve redzone overwritten issue at debug
Subsystems (4)
v5 cover kasan: solve redzone overwritten issue at debug
From: Yee Lee <[email protected]>
Issue: In SLUB debug, hwtag kasan_unpoison() would overwrite the redzone in those objects with unaligned size.
The first patch Introduces slub_debug_enable_unlikely() to check the state of debug mode.
The second patch Adds memzero_explict() to separate the initialization for such condition. The new code path is executed about 1.1% during nromal booting process. The penalty is acceptable since it only works in debug mode.
=============
Exp: QEMUv5.2(+mte)/SLUB_debug mode
code path exec : 941/80854 (1.1%)
Changed since v5:
- Fix format
Changed since v4:
- Introduce slub_debug_enable_unlikly() to check the debug state.
- Include "slab.h" and Add slub_debug_enable_unlikly() to lead the condition statement.
- Add comment block about this new code path in source code.
Changed since v3:
- Apply IS_ENABLED to wrap codes under SLUB debug mode.
- Replace memset() by memzero_explict().
---
Marco Elver (1):
mm: introduce helper to check slub_debug_enabled
Yee Lee (1):
kasan: Add memzero int for unaligned size at DEBUG
mm/kasan/kasan.h | 12 ++++++++++++ mm/slab.h | 15 +++++++++++---- 2 files changed, 23 insertions(+), 4 deletions(-)
Signature · 1 line
2.18.0
PATCH v5 1/2 mm: introduce helper to check slub_debug_enabled
From: Marco Elver <[email protected]>
Introduce a helper to check slub_debug_enabled, so that we can confine the use of #ifdef to the definition of the slub_debug_enabled_unlikely() helper.
--- mm/slab.h | 15 +++++++++++---- 1 file changed, 11 insertions(+), 4 deletions(-)
mm/slab.h +11 -4
@@ -216,10 +216,18 @@ DECLARE_STATIC_KEY_FALSE(slub_debug_enabled);#endif extern void print_tracking (struct kmem_cache *s,void *object);long validate_slab_cache (struct kmem_cache *s); +static inline bool slub_debug_enabled_unlikely (void ) +{ +return static_branch_unlikely (&slub_debug_enabled); +}#else static inline void print_tracking (struct kmem_cache *s,void *object) { } +static inline bool slub_debug_enabled_unlikely (void ) +{ +return false; +}#endif /*
@@ -229,11 +237,10 @@ static inline void print_tracking(struct kmem_cache *s, void *object)*/ static inline bool kmem_cache_debug_flags (struct kmem_cache *s,slab_flags_t flags) { -#ifdef CONFIG_SLUB_DEBUG -VM_WARN_ON_ONCE (!(flags &SLAB_DEBUG_FLAGS )); -if (static_branch_unlikely (&slub_debug_enabled)) +if (IS_ENABLED (CONFIG_SLUB_DEBUG )) +VM_WARN_ON_ONCE (!(flags &SLAB_DEBUG_FLAGS )); +if (slub_debug_enabled_unlikely ())return s->flags & flags; -#endif return false; }
Signature · 1 line
2.18.0
Re: [PATCH v5 1/2] mm: introduce helper to check slub_debug_enabled
Quoted 5 lines · On Mon, Jul 05, 2021 at 10:40:57AM +0800, [email protected] wrote:
From: Marco Elver <[email protected]>
Introduce a helper to check
slub_debug_enabled, so that we can confine the use of #ifdef to the definition of theslub_debug_enabled_unlikely()helper.
We don't usually embed '_unlikely' in function names; we just do:
static inline bool slub_debug_enabled(void)
{
return static_branch_unlikely(&slub_debug_enabled);
}eg:
static inline bool cpusets_enabled(void)
{
return static_branch_unlikely(&cpusets_enabled_key);
}#define cgroup_bpf_enabled(type) static_branch_unlikely(&cgroup_bpf_enabled_key[type])
static inline int ip_tunnel_collect_metadata(void)
{
return static_branch_unlikely(&ip_tunnel_metadata_cnt);
}static inline bool frontswap_enabled(void)
{
return static_branch_unlikely(&frontswap_enabled_key);
}Re: [PATCH v5 1/2] mm: introduce helper to check slub_debug_enabled
Quoted 7 lines · Matthew Wilcox
Quoted 5 lines · On Mon, Jul 05, 2021 at 10:40:57AM +0800, [email protected] wrote:
From: Marco Elver <[email protected]>
Introduce a helper to check
slub_debug_enabled, so that we can confine the use of #ifdef to the definition of theslub_debug_enabled_unlikely()helper.
Quoted 7 lines
We don't usually embed '
_unlikely' in function names; we just do:static inline bool
slub_debug_enabled(void){ return static_branch_unlikely(&slub_debug_enabled); }
The names are identical, this obviously won't work:
In file included from mm/slub.c:21:mm/slab.h:219:20: error: ‘slub_debug_enabled’ redeclared as different kind of symbol
219 | static inline bool slub_debug_enabled(void)
But it seems that someone had the same idea, and this merge window got a __slub_debug_enabled() with 792702911f58.
Yee, can you replace this patch with the below:
From: Marco Elver <[email protected]>
Date: Wed, 30 Jun 2021 20:56:57 +0200
Subject: [PATCH] mm: move helper to check slub_debug_enabled
Move the helper to check slub_debug_enabled, so that we can confine the use of #ifdef outside slub.c as well.
---
v6:
* Move helper instead of introducing a new one.
--- mm/slab.h | 15 +++++++++++---- mm/slub.c | 14 -------------- 2 files changed, 11 insertions(+), 18 deletions(-)
mm/slab.h +11 -4
@@ -216,10 +216,18 @@ DECLARE_STATIC_KEY_FALSE(slub_debug_enabled);#endif extern void print_tracking (struct kmem_cache *s,void *object);long validate_slab_cache (struct kmem_cache *s); +static inline bool __slub_debug_enabled (void ) +{ +return static_branch_unlikely (&slub_debug_enabled); +}#else static inline void print_tracking (struct kmem_cache *s,void *object) { } +static inline bool __slub_debug_enabled (void ) +{ +return false; +}#endif /*
@@ -229,11 +237,10 @@ static inline void print_tracking(struct kmem_cache *s, void *object)*/ static inline bool kmem_cache_debug_flags (struct kmem_cache *s,slab_flags_t flags) { -#ifdef CONFIG_SLUB_DEBUG -VM_WARN_ON_ONCE (!(flags &SLAB_DEBUG_FLAGS )); -if (static_branch_unlikely (&slub_debug_enabled)) +if (IS_ENABLED (CONFIG_SLUB_DEBUG )) +VM_WARN_ON_ONCE (!(flags &SLAB_DEBUG_FLAGS )); +if (__slub_debug_enabled ())return s->flags & flags; -#endif return false; }
mm/slub.c +0 -14
@@ -119,25 +119,11 @@*/ #ifdef CONFIG_SLUB_DEBUG -#ifdef CONFIG_SLUB_DEBUG_ON DEFINE_STATIC_KEY_TRUE (slub_debug_enabled);#else DEFINE_STATIC_KEY_FALSE (slub_debug_enabled);#endif - -static inline bool __slub_debug_enabled (void ) -{ -return static_branch_unlikely (&slub_debug_enabled); -} - -#else /* CONFIG_SLUB_DEBUG */ - -static inline bool __slub_debug_enabled (void ) -{ -return false; -} -#endif /* CONFIG_SLUB_DEBUG */ static inline bool kmem_cache_debug (struct kmem_cache *s)
Signature · 1 line
2.32.0.93.g670b81a890-goog
PATCH v5 2/2 kasan: Add memzero int for unaligned size at DEBUG
In reply to [email protected]From: Yee Lee <[email protected]>
Issue: when SLUB debug is on, hwtag kasan_unpoison() would overwrite the redzone of object with unaligned size.
An additional memzero_explicit() path is added to replacing init by hwtag instruction for those unaligned size at SLUB debug mode.
The penalty is acceptable since they are only enabled in debug mode, not production builds. A block of comment is added for explanation.
--- mm/kasan/kasan.h | 12 ++++++++++++ 1 file changed, 12 insertions(+)
mm/kasan/kasan.h +12 -0
@@ -9,6 +9,7 @@#ifdef CONFIG_KASAN_HW_TAGS #include <linux/static_key.h> +#include "../slab.h" DECLARE_STATIC_KEY_FALSE (kasan_flag_stacktrace);extern bool kasan_flag_async__ro_after_init ;
@@ -387,6 +388,17 @@ static inline void kasan_unpoison(const void *addr, size_t size, bool init)if (WARN_ON ((unsigned long )addr &KASAN_GRANULE_MASK ))return ; +/* +* Explicitly initialize the memory with the precise object size to +* avoid overwriting the SLAB redzone. This disables initialization in +* the arch code and may thus lead to performance penalty. The penalty +* is accepted since SLAB redzones aren't enabled in production builds. +*/ +if (slub_debug_enabled_unlikely () && + init && ((unsigned long )size &KASAN_GRANULE_MASK )) { + init = false; +memzero_explicit ((void *)addr, size); + } size =round_up (size,KASAN_GRANULE_SIZE );hw_set_mem_tag_range ((void *)addr, size, tag, init);
Signature · 1 line
2.18.0