ftrace-unpoison-ftrace_regs-in-ftrace_ops_list_func.patch removed from -mm tree
The quilt patch titled
Subject: ftrace: unpoison ftrace_regs in ftrace_ops_list_func()
has been removed from the -mm tree. Its filename was
ftrace-unpoison-ftrace_regs-in-ftrace_ops_list_func.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: Ilya Leoshkevich <[email protected]>
Subject: ftrace: unpoison ftrace_regs in ftrace_ops_list_func()
Date: Fri, 21 Jun 2024 13:34:45 +0200
Patch series "kmsan: Enable on s390", v7.
Architectures use assembly code to initialize ftrace_regs and call ftrace_ops_list_func(). Therefore, from the KMSAN's point of view, ftrace_regs is poisoned on ftrace_ops_list_func entry(). This causes KMSAN warnings when running the ftrace testsuite.
Fix by trusting the architecture-specific assembly code and always unpoisoning ftrace_regs in ftrace_ops_list_func.
The issue was not encountered on x86_64 so far only by accident:
assembly-allocated ftrace_regs was overlapping a stale partially unpoisoned stack frame. Poisoning stack frames before returns [1] makes the issue appear on x86_64 as well.
[1] https://github.com/iii-i/llvm-project/commits/msan-poison-allocas-before-returning-2024-06-12/
---
kernel/trace/ftrace.c | 1 + 1 file changed, 1 insertion(+)
kernel/trace/ftrace.c renamed from kernel/trace/ftrace.c~ftrace-unpoison-ftrace_regs-in-ftrace_ops_list_func +1 -0
@@ -7407,6 +7407,7 @@ out:void arch_ftrace_ops_list_func (unsigned long ip,unsigned long parent_ip,struct ftrace_ops *op,struct ftrace_regs *fregs) { +kmsan_unpoison_memory (fregs,sizeof (*fregs));__ftrace_ops_list_func (ip, parent_ip,NULL , fregs); }#else
_
Patches currently in -mm which might be from [email protected] are