kasan-support-kasanstacktrace-for-sw_tags.patch removed from -mm tree
The quilt patch titled
Subject: kasan: support kasan.stacktrace for SW_TAGS
has been removed from the -mm tree. Its filename was
kasan-support-kasanstacktrace-for-sw_tags.patch
This patch was dropped because it was merged into the mm-stable branch of git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
------------------------------------------------------
From: Andrey Konovalov <[email protected]>
Subject: kasan: support kasan.stacktrace for SW_TAGS
Date: Mon, 5 Sep 2022 23:05:46 +0200
Add support for the kasan.stacktrace command-line argument for Software Tag-Based KASAN.
The following patch adds a command-line argument for selecting the stack ring size, and, as the stack ring is supported by both the Software and the Hardware Tag-Based KASAN modes, it is natural that both of them have support for kasan.stacktrace too.
---
Documentation/dev-tools/kasan.rst | 15 +++++---- mm/kasan/hw_tags.c | 39 ------------------------- mm/kasan/kasan.h | 36 +++++++++++++++-------- mm/kasan/sw_tags.c | 5 ++- mm/kasan/tags.c | 43 ++++++++++++++++++++++++++++ 5 files changed, 81 insertions(+), 57 deletions(-)
Documentation/dev-tools/kasan.rst renamed from Documentation/dev-tools/kasan.rst~kasan-support-kasanstacktrace-for-sw_tags +9 -6
@@ -111,9 +111,15 @@ parameter can be used to control panic a report or also panic the kernel (default: ``report``). The panic happens even if ``kasan_multi_shot`` is enabled. -Hardware Tag-Based KASAN mode (see the section about various modes below) is -intended for use in production as a security mitigation. Therefore, it supports -additional boot parameters that allow disabling KASAN or controlling features: +Software and Hardware Tag-Based KASAN modes (see the section about various +modes below) support disabling stack trace collection: + +- ``kasan.stacktrace=off`` or ``=on`` disables or enables alloc and free stack + traces collection (default: ``on``). + +Hardware Tag-Based KASAN mode is intended for use in production as a security +mitigation. Therefore, it supports additional boot parameters that allow +disabling KASAN altogether or controlling its features: - ``kasan=off`` or ``=on`` controls whether KASAN is enabled (default: ``on``).
@@ -132,9 +138,6 @@ additional boot parameters that allow di - ``kasan.vmalloc=off`` or ``=on`` disables or enables tagging of vmalloc allocations (default: ``on``). -- ``kasan.stacktrace=off`` or ``=on`` disables or enables alloc and free stack - traces collection (default: ``on``). - Error reports ~~~~~~~~~~~~~
mm/kasan/hw_tags.c renamed from mm/kasan/hw_tags.c~kasan-support-kasanstacktrace-for-sw_tags +1 -38
@@ -38,16 +38,9 @@ enum kasan_arg_vmalloc { KASAN_ARG_VMALLOC_ON, }; -enum kasan_arg_stacktrace { -KASAN_ARG_STACKTRACE_DEFAULT , -KASAN_ARG_STACKTRACE_OFF , -KASAN_ARG_STACKTRACE_ON , -}; -static enum kasan_arg kasan_arg__ro_after_init ;static enum kasan_arg_mode kasan_arg_mode__ro_after_init ;static enum kasan_arg_vmalloc kasan_arg_vmalloc__initdata ; -static enum kasan_arg_stacktrace kasan_arg_stacktrace__initdata ;/* * Whether KASAN is enabled at all.
@@ -66,9 +59,6 @@ EXPORT_SYMBOL_GPL(kasan_mode);/* Whether to enable vmalloc tagging. */ DEFINE_STATIC_KEY_TRUE (kasan_flag_vmalloc); -/* Whether to collect alloc/free stack traces. */ -DEFINE_STATIC_KEY_TRUE (kasan_flag_stacktrace); -/* kasan=off/on */ static int __init early_kasan_flag (char *arg) {
@@ -122,23 +112,6 @@ static int __init early_kasan_flag_vmall }early_param ("kasan.vmalloc" , early_kasan_flag_vmalloc); -/* kasan.stacktrace=off/on */ -static int __init early_kasan_flag_stacktrace (char *arg) -{ -if (!arg) -return -EINVAL ; - -if (!strcmp (arg,"off" )) - kasan_arg_stacktrace =KASAN_ARG_STACKTRACE_OFF ; -else if (!strcmp (arg,"on" )) - kasan_arg_stacktrace =KASAN_ARG_STACKTRACE_ON ; -else -return -EINVAL ; - -return 0 ; -} -early_param ("kasan.stacktrace" , early_kasan_flag_stacktrace); -static inline const char *kasan_mode_info (void ) {if (kasan_mode ==KASAN_MODE_ASYNC )
@@ -213,17 +186,7 @@ void __init kasan_init_hw_tags(void)break ; } -switch (kasan_arg_stacktrace) { -case KASAN_ARG_STACKTRACE_DEFAULT : -/* Default is specified by kasan_flag_stacktrace definition. */ -break ; -case KASAN_ARG_STACKTRACE_OFF : -static_branch_disable (&kasan_flag_stacktrace); -break ; -case KASAN_ARG_STACKTRACE_ON : -static_branch_enable (&kasan_flag_stacktrace); -break ; - } +kasan_init_tags ();/* KASAN is now initialized, enable it. */ static_branch_enable (&kasan_flag_enabled);
mm/kasan/kasan.h renamed from mm/kasan/kasan.h~kasan-support-kasanstacktrace-for-sw_tags +24 -12
@@ -8,13 +8,31 @@#include <linux/kfence.h> #include <linux/stackdepot.h> -#ifdef CONFIG_KASAN_HW_TAGS +#if defined(CONFIG_KASAN_SW_TAGS ) || defined(CONFIG_KASAN_HW_TAGS )#include <linux/static_key.h> + +DECLARE_STATIC_KEY_TRUE (kasan_flag_stacktrace); + +static inline bool kasan_stack_collection_enabled (void ) +{ +return static_branch_unlikely (&kasan_flag_stacktrace); +} + +#else /* CONFIG_KASAN_SW_TAGS || CONFIG_KASAN_HW_TAGS */ + +static inline bool kasan_stack_collection_enabled (void ) +{ +return true; +} + +#endif /* CONFIG_KASAN_SW_TAGS || CONFIG_KASAN_HW_TAGS */ + +#ifdef CONFIG_KASAN_HW_TAGS +#include "../slab.h" DECLARE_STATIC_KEY_TRUE (kasan_flag_vmalloc); -DECLARE_STATIC_KEY_TRUE (kasan_flag_stacktrace);enum kasan_mode { KASAN_MODE_SYNC,
@@ -29,11 +47,6 @@ static inline bool kasan_vmalloc_enabledreturn static_branch_likely (&kasan_flag_vmalloc); } -static inline bool kasan_stack_collection_enabled (void ) -{ -return static_branch_unlikely (&kasan_flag_stacktrace); -} -static inline bool kasan_async_fault_possible (void ) {return kasan_mode ==KASAN_MODE_ASYNC || kasan_mode ==KASAN_MODE_ASYMM ;
@@ -46,11 +59,6 @@ static inline bool kasan_sync_fault_poss#else /* CONFIG_KASAN_HW_TAGS */ -static inline bool kasan_stack_collection_enabled (void ) -{ -return true; -} -static inline bool kasan_async_fault_possible (void ) {return false;
@@ -410,6 +418,10 @@ static inline void kasan_enable_tagging(#endif /* CONFIG_KASAN_HW_TAGS */ +#if defined(CONFIG_KASAN_SW_TAGS ) || defined(CONFIG_KASAN_HW_TAGS ) +void __init kasan_init_tags (void ); +#endif /* CONFIG_KASAN_SW_TAGS || CONFIG_KASAN_HW_TAGS */ +#if defined(CONFIG_KASAN_HW_TAGS ) &&IS_ENABLED (CONFIG_KASAN_KUNIT_TEST )void kasan_force_async_fault (void );
mm/kasan/sw_tags.c renamed from mm/kasan/sw_tags.c~kasan-support-kasanstacktrace-for-sw_tags +4 -1
@@ -42,7 +42,10 @@ void __init kasan_init_sw_tags(void)for_each_possible_cpu (cpu)per_cpu (prng_state, cpu) = (u32 )get_cycles (); -pr_info ("KernelAddressSanitizer initialized (sw-tags)\n" ); +kasan_init_tags (); + +pr_info ("KernelAddressSanitizer initialized (sw-tags, stacktrace=%s)\n" , +kasan_stack_collection_enabled () ?"on" :"off" ); }/*
mm/kasan/tags.c renamed from mm/kasan/tags.c~kasan-support-kasanstacktrace-for-sw_tags +43 -0
55 lines not on this page · raw message
_
Patches currently in -mm which might be from [email protected] are
kasan-fix-array-bounds-warnings-in-tests.patch