kasan-drop-skip_kasan_poison-variable-in-free_pages_prepare.patch removed from -mm tree
The patch titled
Subject: kasan: drop skip_kasan_poison variable in free_pages_prepare
has been removed from the -mm tree. Its filename was
kasan-drop-skip_kasan_poison-variable-in-free_pages_prepare.patch
This patch was dropped because it was merged into mainline or a subsystem tree
------------------------------------------------------
From: Andrey Konovalov <[email protected]>
Subject: kasan: drop skip_kasan_poison variable in free_pages_prepare
skip_kasan_poison is only used in a single place. Call should_skip_kasan_poison() directly for simplicity.
---
mm/page_alloc.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-)
mm/page_alloc.c renamed from mm/page_alloc.c~kasan-drop-skip_kasan_poison-variable-in-free_pages_prepare +1 -2
@@ -1297,7 +1297,6 @@ static __always_inline bool free_pages_p unsigned int order, bool check_free, fpi_t fpi_flags) { int bad = 0; -bool skip_kasan_poison =should_skip_kasan_poison (page, fpi_flags);bool init =want_init_on_free ();VM_BUG_ON_PAGE (PageTail (page), page);
@@ -1371,7 +1370,7 @@ static __always_inline bool free_pages_p* With hardware tag-based KASAN, memory tags must be set before the * page becomes unavailable via debug_pagealloc or arch_free_page. */ -if (!skip_kasan_poison) { +if (!should_skip_kasan_poison (page, fpi_flags)) {kasan_poison_pages (page, order, init);/* Memory is already initialized if KASAN did it internally. */
_
Patches currently in -mm which might be from [email protected] are
stacktrace-add-interface-based-on-shadow-call-stack.patch arm64-scs-save-scs_sp-values-per-cpu-when-switching-stacks.patch arm64-implement-stack_trace_save_shadow.patch kasan-use-stack_trace_save_shadow.patch